chore(release): stamp 1.10.1 - #40
Merged
Merged
Conversation
PATCH is the smallest valid scope, and the correct one. Both changes in this release are bug fixes to behaviour that was already wrong: a scan rule that reported a REVOKE as an unscoped read, and two QA scenarios asserting an exit code that stopped being correct when the testing gate became blocking in 1.9.0. Version Scope Decision: - Chosen bump: PATCH - Why not smaller: there is nothing smaller; a released false-positive rule and a permanently-red pre-push stage both need to reach users. - Breaking impact: none. No CLI flag, output key, or exported symbol changed. `forge scan security` reports strictly fewer findings than 1.10.0 on the same input, and every finding it stops reporting was wrong. No BREAKING.md entry: nothing in this release breaks a contract. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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 v1.10.1 — a pure PATCH release over
v1.10.0, containing the two bug fixes merged in #39.Version Scope Decision
PATCHREVOKEas an unscoped read, and a pre-push stage that has been permanently red since 1.9.0, both need to reach users.forge scan securityreports strictly fewer findings than 1.10.0 on the same input, and every finding it stops reporting was wrong.No
BREAKING.mdentry: nothing in this release breaks a contract.What ships
fix(scan)—RunRLSscans whole files in two passes soselect-without-where-tenantno longer flagsGRANT/REVOKEstatements or reads of a CTE the same statement populated.TC-SCAN-RLS-07pins that the exemption cannot become an off switch for the rule.fix(qa)— QA-24 and QA-26 pass--no-strict-testing, the documented waiver, so a scratchforge init --minimalproject no longer fails a four-stage testing audit it was never meant to satisfy.Verification
go build ./...andgo test ./...— green, 0 failures.After merge:
make tag VERSION=1.10.1→git push origin v1.10.1→ goreleaser + npm publish.🤖 Generated with Claude Code