May 2024 Changelog
Welcome to our May changelog, where we share the latest feature updates and improvements from DevCycle. This month, we've focused on enhancing our integrations, improving performance for server-side rendering, and introducing a new way to manage complex schedules and variations with Passthrough Rollouts.
If you want to read ahead on what we're building next check out our public roadmap.
🪝 Slack & Webhooks: Subscribe to Specific Environment Changes
We've shipped an enhancement to our Slack integration and outbound webhooks, allowing you to subscribe to specific environment changes. This update helps minimize noise in your feed channels, ensuring you only receive the most relevant information.
To add a subscription for project or feature changes in a specific environment using our Slack integration, simply add the flag [-e environment-key] to the Slack command. For more details on setting up and using our Slack integration, check out our documentation.
👢 SDK Bootstrapping & Server-Side Rendering
When using server rendering frameworks like Remix, Nuxt, or SvelteKit, it's crucial to ensure that the rendering on the server uses the same flag values as the client. Additionally, it's important to minimize the performance impact of the initial client-side DevCycle configuration fetch that would normally occur when the page is first loaded.
To address these concerns, we're introducing SDK bootstrapping for all Javascript-based SDKs. This feature helps teams ensure the best possible performance when leveraging DevCycle in a server-side rendering context. To learn more about SDK bootstrapping and how to implement it in your projects, visit our bootstrapping documentation.
⬇️ Passthrough Rollouts
Passthrough Rollouts is a new feature that allows users to be evaluated against subsequent rules if a rollout or schedule hasn't been hit for them. Instead of being "held" on the first rule, users can be served the targeting of subsequent rules. This makes managing complex schedules and variation changes for the same audience much easier.
If your team is actively using the Scheduled Rollouts functionality for Targeting Rules, this change may affect how Targeting Rules behave for your Features. For server-side SDKs, we recommend upgrading your SDK before turning Passthrough Rollouts on. Client-side SDK users can opt-in whenever they'd like without an SDK update and start using the new targeting rule behaviour immediately.
For more information on Passthrough Rollouts and the required server-side SDK versions, please refer to our documentation.
We hope you find these updates and improvements valuable for your feature flagging workflows. As always, we welcome your feedback and feature requests. Feel free to post your feature requests or upvote features on our roadmap.