Automate npm release docs, pack verification, and provenance - #133
Merged
Merged
Conversation
…shing Add scripts/update_release_docs.mjs to generate Keep a Changelog entries from git history and refresh the README release-docs block. The Release workflow now updates CHANGELOG.md and README before publish, dry-runs npm pack, publishes with npm provenance, syncs docs back to main, and uses changelog content for GitHub Release notes. CI verifies npm pack on Node 20. Co-authored-by: Jeremy McSpadden <jeremy@fluxlabs.net>
…eases Introduce scripts/bump_version.mjs to derive the next semver from commits since the previous v* tag (breaking -> major, feat -> minor, fix/perf -> patch) or from an explicit bump input. Manual Release dispatch can now omit version and choose auto/major/minor/patch; the workflow commits the bump to main before verify and publish. Tag pushes still require a pre-bumped package.json. Co-authored-by: Jeremy McSpadden <jeremy@fluxlabs.net>
…ertions Disable history recording in the ServeTests fixture and stop the background poll thread on teardown. test_activity now asserts the seeded phase-changed event instead of the full history length, removing a CI flake where the first poll appended a project-added record before the assertion ran. Co-authored-by: Jeremy McSpadden <jeremy@fluxlabs.net>
jeremymcs
marked this pull request as ready for review
September 20, 2026 08:32
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.
Summary
Enhances the Release workflow with automated changelog/README updates, npm publishing best practices, and conventional-commit auto version bumping.
Auto version bump
scripts/bump_version.mjs— derives next semver from commits since the previousv*tag:BREAKING CHANGE/type!:→ major (1.1.0→2.0.0)feat:→ minor (1.1.0→1.2.0)fix:/perf:→ patch (1.1.0→1.1.1)auto/major/minor/patchmain, then verifies, publishes, and tagspackage.jsonto already match the tagRelease docs + publish hardening
CHANGELOG.md+ README release block before publishnpm pack --dry-runin CI and releasenpm publish --provenancemain; GitHub Release notes from changelogPreview locally
Test plan
npm test(89 tests pass)node scripts/bump_version.mjs --bump auto --dry-runon currentmain