Roll back feature configuration with Git

A Featurevisor configuration rollback is a new configuration release. Revert the intended definition change in Git, run validation and tests, then publish the resulting datafiles. Applications receive the correction when they refresh.

Revert the definition change#

For an ordinary commit containing the unwanted configuration change:

git switch -c revert-checkout-config
git revert <configuration-commit>
npx featurevisor lint
npx featurevisor test
npx featurevisor build

Replace the placeholder with the commit you reviewed. If the commit contains unrelated work, prepare a narrower correction instead. Merge commits require additional care when choosing what to revert.

Review the new diff and use your normal repository approval and deployment process. Git history then records both the original change and its reversal.

Keep allocation state intact#

State files preserve allocation history. Reverting a definition does not mean deleting state files or restoring arbitrary old allocation state. Keep the established build workflow so the builder can maintain stable allocations.

Check the feature and variable outcomes you intend to restore through test specifications. Include boundary cases when percentages or variations changed.

Publish the correction#

Publish all affected environment and Target datafiles. A successful Git merge alone does not update running applications.

For consumers loading a complete datafile, f.setDatafile(datafile, true) replaces the existing definitions. An ordinary merge retains definitions absent from the incoming datafile, so it is not sufficient when the correction needs to remove an entity.

Coordinate CDN caching and application refresh intervals with your recovery needs. Verify the revision and a representative evaluation after the new file reaches an application.

Prepare before an incident#

Keep previous deployment artifacts according to your release policy and know which environments they represent. Redeploying an earlier artifact can be a deliberate recovery action, but review its complete contents and compatibility rather than assuming only one flag changed.

The Cloudflare example demonstrates publishing datafiles. The deployment guide explains distribution options, and offline evaluation covers applications that cannot receive the correction immediately.