fix(flag-release): correct immediate-release timing in auto-release reference - #140
Open
stasquatch wants to merge 1 commit into
Open
fix(flag-release): correct immediate-release timing in auto-release reference#140stasquatch wants to merge 1 commit into
stasquatch wants to merge 1 commit into
Conversation
…eference The reference said simple serves true as soon as the config is created. Immediate (simple) releases now release when flag evaluations are detected, same as policy releases, so this was misleading agents into reporting a release before released_at was actually set. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Skill eval results
Only suites whose source actually changed since their last recorded score were re-run. Soft-failing while we stabilise the baseline. |
stasquatch
marked this pull request as ready for review
July 31, 2026 15:41
stasquatch
requested review from
RobertPakkoLD,
dariushar,
davidbrackbill,
nieblara and
vroske-ld
July 31, 2026 15:41
davidbrackbill
approved these changes
Jul 31, 2026
stasquatch
enabled auto-merge (squash)
July 31, 2026 15:45
dariushar
approved these changes
Jul 31, 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
3 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
references/auto-release.mddescribedsimplerelease type as servingtrue"as soon as the config is created." That's stale: immediate (simple) releases now release when flag evaluations are detected, the same triggerpolicyalready correctly waits for in this same doc —simplejust skips policy resolution and stages.launchdarkly/gonfalon(.agents/skills/gonfalon-flag-rollout/SKILL.md, merged) andlaunchdarkly/gram-functions(create-automated-rollout-configtool description, PR #168).Test plan
via LD Research 🤖
Note
Low Risk
Markdown reference-only change with no runtime or API behavior impact.
Overview
Updates
references/auto-release.mdso thesimplerelease type is documented correctly: it turns the flag on when flag evaluation starts, not when the automated rollout config is created.That matches how
policyis already described in the same doc—simplejust skips policy resolution and staged rollout—and avoids misleading guidance that staging/production could flip before merged code is actually evaluating the flag.Reviewed by Cursor Bugbot for commit c9dc1ae. Bugbot is set up for automated code reviews on this repo. Configure here.