Release 8.6.0: announce the /flow-reviewer deprecation - #84
Merged
Merged
Conversation
The /flow-reviewer deprecation has been on main since #82 but no published version carries it. The cadence rule requires a surface to be announced in one release before a major removes it, so 9.0.0 cannot drop the command until this ships. Frozen surface for the offline qualification that follows: this commit holds the final package.json, README pins and changelog, so the release record can name it as the reviewed commit without any later edit moving a frozen blob. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Authorize 8.6.0 through the offline feature exception, frozen to 4c59cdd. The runtime is byte-identical to the reviewed 8.5.0 picker sources apart from one palette title; the rest of the diff is documentation, so the frozen file list is reused and only the reviewed commit advances. The retained 8.5.0 seal could not be reused: the grader closure covers package.json, so the version bump alone invalidated it. Regrade the same original 8.3.0 campaign and canary offline, with no model calls. This is the third consecutive offline release and the operator accepted that knowingly. The baseline stays 8.3.0; offline releases never become baselines. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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.
Cuts 8.6.0 so 9.0.0 can remove
/flow-reviewer.Why this release exists
docs/release-qualification.md:82requires a surface that is going away to be announced in one release and removed no earlier than the next major. The deprecation landed on main in #82, but no published version carries it —v8.5.0predates it. Without this release, 9.0.0 would take users from 8.5.0 (command works, no warning they'd ever see) straight to a version where it's gone, which is exactly the stranding that rule prevents.Qualification
Third consecutive offline release, authorized knowingly after being shown that a funded live campaign and holding the release were the alternatives. Frozen to
4c59cdd, which holds the final manifest, README pins and changelog.The frozen file list is reused from 8.5.0 unchanged — this release alters no picker source except one palette title, so only the reviewed commit advances.
The retained 8.5.0 seal could not be reused: the grader closure covers
package.json, so the version bump alone invalidated it. The same original 8.3.0 campaign and canary were regraded offline into.agents/plans/11-reviewer-deprecation-release/baselines, with no model calls. New sealsha256:05ca1708….The baseline stays 8.3.0. Offline releases never become baselines, so four releases now sit between this candidate and the last live measurement. The generated notes say so explicitly:
Verification
bun run check— 1214 pass, 1 skip, 0 fail.bun scripts/release.ts init … --feature evals/qualification/features/8.6.0.json— Release record verified.f92d406f…reproduces the value bound in the record.One test fixture changed:
tests/feature-release.test.tslisted8.6.0among versions an entry must reject, which stopped holding once 8.6.0 became an authorized version. It now skips each entry's own version and adds8.7.0.🤖 Generated with Claude Code