CloudBees Feature Management - Go changelog

CloudBees Feature Management is an advanced feature flagging solution that lets your development teams quickly build and deploy applications without compromising on safety. By providing a gradual release mechanism and a simple way to define target audiences, CloudBees Feature Management allows developers and product managers to optimize feature releases and customize the user experience. CloudBees Feature Management gives teams control over features that are in staging, production, or any environment in the deployment pipeline.

This is legacy documentation

CloudBees Feature Management is now part of CloudBees Unify. For current feature management documentation, go to CloudBees Unify Feature management.

This documentation covers the original CloudBees Feature Management product (formerly Rollout.io), which is end-of-life. It remains available only for existing customers who are migrating to CloudBees Unify.
Support during the extension period

Because CloudBees Feature Management is an end-of-life product, support during the extension period is limited to critical items only:

  • Critical security fixes: High-impact security issues are in scope and will be addressed.

  • Critical bug fixes: Reviewed case by case; resolution is not guaranteed.

  • General support, enhancements, and non-critical fixes: Not provided for end-of-life products during the extension period.

This coverage is consistent with the CloudBees end-of-life policy in the support Terms & Conditions.

June 13, 2025: V6.0.1

Fixes and additions:

  • Fix bug with impressions reporting.

September 24, 2024: V6.0.0

Fixes and additions:

  • Official release with support for CloudBees Platform.

June 13, 2024: V5.0.11

Fixes and additions:

  • Internal updates to support CloudBees Platform.

March 27, 2023: V5.0.5

Fixes and additions:

  • Fixed background configuration fetcher process so it can correctly continue after a single iteration.

January 25, 2023: V5.0.4 Adding alternative flag name via flagName tag

Breaking changes:

  • Setting a flagName tag on a flag in a Container structure changes the flag name. The flag is now a completely new flag and needs to be configured.

January 25, 2023: V5.0.3 Allowing customized network urls

2021-04-30: V5.0.0

Breaking changes:

  • Variant changed to RoxString

    • Variant("default_string", ['string_1', 'string_2']) ⇒ RoxString('default_string', ['string_1', 'string_2'])

Fixes and additions:

  • New register without a namespace:

    • rox.RegisterWithEmptyNamespace(container) will register the container under an empty string namespace (multiple register calls with the same namespaces are still not allowed).

  • Impressions

    • Starting with SDK 5, flags will always send impressions after setup (not only when targeting is enabled on the dashboard).

  • Impression handler parameters change

    • As experiments were removed, impressions handler signature was changed from (ReportingValue, Experiment, Context) to (ReportingValue, Context). ReportingValue now also has a Targeting (boolean) property, indicating the flag was evaluated by using the dashboard configurations.

  • New Flag Types Int/Double

    • In addition to server.RoxFlag and server.RoxString, we also added server.RoxInt and server.RoxDouble

    • DynamicApi was also updated with matching GetInt and GetDouble methods

  • Added a graceful rox.Shutdown

    • In order to clean all background tasks, multiple rox.Setup calls will be ignored. If Rox wasn’t shut down in between, rox.Shutdown calls are ignored if Rox is not running or corrupt.

  • Fix RegEx Match condition and empty string values

2019-09-02

  • Changes to API calls, using Cloudfront

  • Added checks on API key format

2018-11-22

  • Dynamic API for flags

2018-11-08

  • Added push updates support

2018-10-04:

Initial release