docs: add Feature Versioning v2 guide and EF_VERSION audit type#7477
Merged
Conversation
Documents what changes for customers when an environment is migrated to Feature Versioning v2 — the supported write endpoints, the new NEW_VERSION_PUBLISHED webhook event, the EF_VERSION audit-log type, the shifts to plan-limit accounting and change-request payload shape, and the surfaces that are unchanged (SDK output, identity overrides). Also extends the Audit Logs page with the EF_VERSION related_object_type and the per-type field-population rules.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
- Lead now mirrors the UI's "attach versions to feature values and segment overrides" wording instead of the recursive "records each published change as a version of that flag". - Drops bullet-trailing editorial: "gives you explicit control...", "Add this event to your consumer's schema...", "invisible to dashboard users in practice". - Drops the speculative "test in a non-production environment first" recommendation from the Migration section.
github-actions
Bot
added
docs
- Drop the Plan-limit accounting section and Dashboard section. Plan caps and dashboard affordances are out of scope for a page aimed at automation, webhook and audit-log consumers. - Drop the What's next? cross-link block. Related pages are linked inline where they are relevant. - Drop residual dashboard references in the lead paragraph and §4.
gagantrivedi
force-pushed
the
docs/feature-versioning-v2-guide
branch
from
8aaa244 to
cc7778f
Compare
Rewords §3 so the Audit Log Webhook is the primary frame (the only programmatic ingestion path Flagsmith documents). Heading, lead sentence, table row label and bullet checklist all switch to webhook terminology. Drops the "expect fewer webhook deliveries" bullet — the volume drop is implicit from the per-change-request table row.
4 tasks
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
There was a problem hiding this comment.
Claude Code Review
This repository is configured for manual code reviews. Comment @claude review to trigger a review and subscribe this PR to future pushes, or @claude review once for a one-time review.
Tip: disable this comment in your organization's Code Review settings.
Holmus
previously approved these changes
May 12, 2026
Holmus
approved these changes
May 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
docs/managing-flags/feature-versioning.mddescribing what changes for webhook consumers, audit-log pipelines, and Admin API scripts when Feature Versioning v2 is enabled.docs/administration-and-security/governance-and-compliance/audit-logs.mdwith theEF_VERSIONrelated_object_typeand per-type rules for howrelated_object_idandrelated_object_uuidare populated.