chore: prepare release v1.10.9 - #49
Merged
Merged
Conversation
Version Scope Decision - Chosen bump: PATCH - Why not smaller: n/a (smallest scope) - Breaking impact: none. The generic-bearer rule reports fewer findings (fixture and doc placeholders only; opaque secrets and every provider-specific rule are unchanged); ScanResult gains an additive `waived` field; forge scan and the ship checkpoint now honour the existing .forge/waivers registry, which is a no-op when the directory is absent. Contents: #48 (waivers wired into the scanner, generic-bearer placeholder recognition, IsWaived renewal fix, docs). Known pre-existing failing test recorded in the CHANGELOG (TestCmd_Subcommand_Verify_JSON). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Signed-off-by: VietKing <likeawind510@gmail.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.
This PR addresses:
Release prep for v1.10.9, following
docs/RELEASE_GUIDE.md§1. CHANGELOG-only; nothing else changes.Scope
Checklist
git commit -sgo test ./...on merged main: 76 of 77 packages pass; the one failure is pre-existing and unrelated (below).Version Scope Decision (RELEASE_GUIDE §1.1)
generic-bearerreports fewer findings (fixture/doc placeholders only; opaque secrets and every provider-specific rule unchanged).ScanResultgains an additivewaivedfield. Waivers are honoured only if.forge/waivers/exists, so projects without it see no change.Known pre-existing test failure (recorded in the CHANGELOG, not fixed here)
TestCmd_Subcommand_Verify_JSONininternal/cli/cmdshipfails on any checkout with no diff againstmain: it runsverifywithout--root, so it inspects the checkout itself, and since 1.10.8shipwarns "nothing to ship" there. Reproduced at22ff658(the commit v1.10.8 was released from), which is why the nightly macOS/Windows jobs are red. It does not gaterelease.yml(v1.10.8 released from that commit).After merge
Tag
v1.10.9on the merge commit (make tag VERSION=1.10.9, thengit push origin v1.10.9);release.ymlpublishes the GitHub release and npm packages.🤖 Generated with Claude Code