Changelog

Making a world-class product requires continuous care and attention to detail. We want Bucket to be a high-quality product that’s robust, reliable, and intuitive to use.

That’s why we’re spending the next five weeks polishing our UI, SDKs, and backend.

Here’s what we polished this week:

App improvements

• Overhauled the code instructions block. It’s simpler and actively listens for real-time checks or usage tracking.
• New card design for the Analyze widgets.
• New card design for the Targeting environment rules.
• Simplified headers across the app.
• A rounded border-radius was added to buttons, inputs, and cards.

SDKs

Node SDK

• Now, it automatically sends user and company details to Bucket when either bindClient or getFeature(s) calls are made. This ensures that up-to-date information is pushed to Bucket so companies can be used immediately. Previously, you had to call updateCompany and updateUser manually.
• Introduced the enableTracking option to disable the sending of track, user, company, and flag events. This is useful when you’re impersonating other users, for example.

Browser/React SDK

• Send feedback using the feature key instead of the feature ID.

Bug fixes

• Streamlined the STARS funnel step icons.
• Filters no longer show errors when you open the popover.

Happy shipping!

We’ve just added release stages to make it simpler to gradually release features. Release stages let you configure your commonly used targeting rules so you can easily apply them to features as you roll them out. 

New apps come with 4 default release stages: In development, Internal, Beta, and General availability. 

They support the common use case of taking a feature from development to internal testing to an optional beta testing phase then finally releasing to everyone.

Stages also make it easy for your team to see which rollout stage a feature has reached.

A stage consists of a name, color, set of targeting rules, and rollout percentage. 

Targeting rules in Bucket let you target:

• A segment of companies
• Individual companies
• Individual users
• Custom contexts

You can edit or delete release stages under Settings. 

To apply a stage to a feature, go to the Targeting tab and select a release stage. You have complete flexibility to add custom targeting rules for individual features. 

Happy shipping!

We’ve rolled out remote attributes to make Bucket faster and easier to implement. Company and user attributes stored on our servers can now be used when evaluating feature flags.

The introduction of remote attributes means that rather than having to fetch or compute all the required attributes each time a feature flag is evaluated, you only need to provide the Company ID and User ID when fetching features.

Attributes in Bucket are updated when they change, via the SDK, or periodically from your backend via the API.

Like so:

With remote attributes you can:

• Set the company plan attribute according to the customer subscription plan from your backend and then gate features access based on the plan from anywhere in your application.
  
• Use an attribute called betaUser: true to gate who gets access to beta features. Then allow users to opt-in to beta features using a button in your application that simply sets the attribute in Bucket.
  
• Integrate with your back office system to set a list of the add-ons that the customer has bought through an attribute in Bucket. For example: addOns: [‘copilot-addon’, ‘ sso’] which you can then use in feature targeting.

Company and user attributes stored in Bucket are automatically used when evaluating feature flags in the case of our browser-based SDKs and can optionally be used in the server-based SDKs. 

Setting remote attributes is a simple method call using our Node SDK. You can also set attributes through our Segment integration which allows you to continue using your existing setup.

By default, attributes are replicated to multiple locations across the globe in our global infrastructure to keep initial evaluation round-trip times low. 

However, you have the option to keep your data exclusively within the EU if you need to adhere to certain data protection regulations.

Happy shipping!

We’ve made it easy to detect stale feature flags by adding the “Last check” column to feature views. 

The "Last check” column lets you confirm that you’ve properly removed the feature's key from your codebase and that checks are no longer firing. 

What's a check exactly? A check is fired from the Bucket SDK whenever a user reaches code that's gated by a Bucket feature key in your app. The "Last check" column shows checks across all of your environments and is fired regardless of the check result (access granted or not).

Happy shipping!

We’ve just added feature descriptions to Bucket. Document each feature’s functionalities with full markdown support.

All the common syntax is supported including *italics*, **bold**, [link](https://example.com), and 'code'.

‍
Feature descriptions appear in a sidebar on the Feature tabs.

Happy shipping!

We’ve finished a comprehensive refactoring of our data tables, mainly used on feature views and segments, to significantly improve performance. 

We’ve also improved the UX by making URLs shareable.

These updates have:

• Drastically improved performance of the data tables (up to 2x)
• Greatly improved data fetching
• Resolved some data persistence issues
• Shareable URLs
  ‍

Happy shipping!

We’ve made it possible for non-Google SSO users to get started with Bucket. You can now sign up with Google or a regular email and password.

If you have a Google account, keep using the single sign-on option like before.

Thanks to Clerk for making it easy to add authentication methods! 

Happy shipping!

We’ve made it easier to see which features have automated feedback surveys activated. 

Features collecting user feedback now have an icon to the right of the name in the Features tab. 

The no-code feedback surveys give your metrics valuable context and surface issues by automatically asking users for feedback after they’ve used a feature a meaningful number of times.

This lets you see which features are gathering automated feedback at a glance. 

Happy feedback collecting!

We’ve made it easy and low-risk to migrate to Bucket with our OpenFeature Node.js and Browser SDKs. 

OpenFeature’s vendor-agnostic feature flagging API makes implementing Bucket faster and without the risk of being locked in. 

If you already use an OpenFeature SDK, it’s simple to plug in Bucket and get started.

Those using React (with or without Next.js) just need to plug our OpenFeature Browser Provider into the OpenFeature React SDK. Our Next.js example shows you how.

Join the OpenFeature community at openfeature.dev.

Happy shipping!

We’ve made it simpler to invite your colleagues to Bucket. Anyone who signs up for Bucket with an email address under your company domain will automatically join your organization.

Bucket checks the verified Google SSO domain when a new user signs up for Bucket. If the domain matches, they are automatically added to the existing organization.

You no longer need to share a Bucket invite link with your teammates. Instead, simply direct them to the login page.

Happy Shipping!