Release 9.0.0: remove the deprecated /flow-reviewer command - #86
Merged
Merged
Conversation
8.6.0 announced the /flow-reviewer deprecation, so the major may now remove it. This commit holds the final package.json, README pins and changelog, so the release record can name it as the reviewed commit without a later edit moving a frozen blob. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Authorize 9.0.0 through the offline feature exception, frozen to f2d92b8. The candidate deletes one palette command and renames the TUI module id; no other runtime behavior changes, so the frozen file list is reused and only the reviewed commit advances. Regrade the same original 8.3.0 campaign and canary offline: the grader closure covers package.json, so the version bump invalidated the 8.6.0 seal. This is the fourth consecutive offline release and the operator accepted that knowingly. Five releases now sit between the candidate and the last live measurement. The baseline stays 8.3.0. 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 9.0.0, removing
/flow-reviewer. Follows #85 (the removal) and #84 (8.6.0, which announced the deprecation).Breaking changes
/flow-reviewerno longer exists./flow-modelsopens the same review picker and also selects the optional planning specialist.opencode-plugin-flow.reviewer-pickertoopencode-plugin-flow.model-picker. Normal plugin registration is unaffected; only tooling referencing the module id directly needs updating.Saved reviewer and planning preferences are untouched — both are read from the same agent options, so no reselection is needed after upgrading.
Qualification
Offline, as authorized. This is the fourth consecutive offline release, and I said plainly before starting that it is the weakest claim yet on an exception written for individually reviewed features. Recording that here so the decision is legible later, not to relitigate it.
Frozen to
f2d92b8, which holds the final manifest, README pins and changelog. The frozen file list is reused from 8.5.0/8.6.0 unchanged — this release deletes one palette command and changes one identifier string, so only the reviewed commit advances.The 8.6.0 seal could not be reused: the grader closure covers
package.json, so the version bump alone invalidated it. Same original 8.3.0 campaign and canary regraded offline, no model calls. New sealsha256:26f58d9f….Nothing in
assertOfflineFeatureScopeconstrains the major or minor, unlikeassertPatchScope. That is what makes this mechanically possible; it is not evidence that it is well measured.The gap this widens
Baseline stays 8.3.0 — offline releases never become baselines. Five releases now sit between this candidate and the last live measurement. The notes say so:
For the next release I'd recommend funding a campaign. A qualified release becomes a new baseline, which resets
OFFLINE_FEATURE_BASELINE, restores the patch path that has been unavailable since 8.4.0, and ends a disclosure that has grown from one release behind to five.Verification
bun run check— 1219 pass, 1 skip, 0 fail.bun scripts/release.ts init … --feature evals/qualification/features/9.0.0.json— Release record verified.2d7539bb…reproduces the value bound in the record.🤖 Generated with Claude Code