# Changelog

## Follow along with updates and improvements made to Doppler.

### [April '26 product update](https://www.doppler.com/changes/april-26-product-updates)

Your logs just got a passport, your CLI got a memory, and your identity layer learned a few new tricks.

This month, we're making it easier to route activity logs wherever they need to go with multiple destinations per service, adding AWS SQS support, unlocking more precise identity matching with nested OIDC claims, and more.

## Multi-destination Activity Log forwarding

You can now configure multiple webhook endpoints for Generic HTTPS, Slack, Discord, and Microsoft Teams, each with independent names, URLs, credentials, and enabled/disabled states. [Learn More.](https://docs.doppler.com/docs/workplace-logs)

## What else have we been up to?

- Doppler CLI [v3.76.0](https://github.com/DopplerHQ/cli/releases/tag/3.76.0) has been released to support fallback files and caching when mounting to any file format.

- Added [AWS SQS](https://docs.doppler.com/docs/aws-sqs) as an activity log forwarding destination for Enterprise customers.

- Added support for nested claims with [OIDC identity authentication](https://docs.doppler.com/docs/service-account-identities). You can now use JSON Pointer syntax (e.g., /realm_access/roles) to reference nested fields in identity provider tokens for claim matching.

- Added the ability to sync directly to [Supabase](https://docs.doppler.com/docs/supabase) branches within a Supabase project.

- Users can now add and create syncs directly from the Integrations page, instead of per-project, in addition to individual projects.

- [Change Request](https://docs.doppler.com/docs/change-requests) approval state is now shown in a pill badge for improved visibility.

- Fixed a validation bug that blocked the creation of new [CircleCI](https://docs.doppler.com/docs/circleci) integration connections.