chore(release): prepare 4.7.0 - #332
Merged
Merged
Conversation
Cut 4.7.0 from the six commits merged since 4.6.3. Two are feature work, so this is a minor bump; the version bump is the Release workflow's signal to tag, publish to npm, and cut the GitHub Release on merge. Added - Reports publish through the git-data API (#328). - styleproof-init prunes reports by API with a retention + size-budget sweep (#329). - CERTIFICATION_FAILED dogfooded end-to-end (#327). Security - Cleared two high-severity transitive advisories: brace-expansion 5.0.6→5.0.7 (#330) and fast-uri 3.1.3→3.1.4, GHSA-v2hh-gcrm-f6hx (#331). Verified locally: build, typecheck, lint, format:check, privacy:check all clean; full node --test suite 630/630 with a complete install. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
🗺️ StyleProof report📊 View the side-by-side visual report →Coverage, determinism, or report/diff consistency evidence is incomplete — repair the capture or reflow source; visual approval cannot clear this failure. |
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
1 participant
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.
Why does this feature exist?
Six commits have merged since 4.6.3 and none are released. Two are feature work (#328, #329), so under semver this is a minor bump. The Release workflow publishes on merge to main whenever
package.json's version has no tag yet — so this PR is the deliberate "release 4.7.0" signal: it bumps the version and moves the accumulated[Unreleased]notes into a dated[4.7.0]section.What changed?
package.json+package-lock.json: version 4.6.3 → 4.7.0 (npm version minor, no code change).CHANGELOG.md: new[4.7.0] - 2026-07-22section grouping the merged work — Added (report publish via the git-data API feat(action): publish reports through the git-data API #328,styleproof-initreport prune feat(init): prune reports by API with a retention and size-budget sweep #329,CERTIFICATION_FAILEDdogfood test(action): dogfood CERTIFICATION_FAILED end-to-end #327) and Security (brace-expansion fix(deps): resolve the brace-expansion audit advisory #330 and fast-uri fix(deps): resolve the fast-uri high-severity audit advisory #331 high-severity transitive advisories cleared).[Unreleased]is reset to empty.Behavioural Proof (with video and screenshots)
Not applicable: a version bump plus CHANGELOG prose, no rendered surface. Proof is the green release gate and the Release workflow tagging
v4.7.0and publishing on merge.Verification Summary
npm run build,typecheck,lint,format:check,privacy:check: all clean.node --testsuite: 630 pass, 0 fail (against a completenpm ciinstall).package.json/package-lock.jsonand the CHANGELOG section.