feat(release): semantic-release automation and 0.2.0 changelog - #1
Merged
Conversation
andreas-timm
force-pushed
the
feature/release
branch
from
July 4, 2026 12:56
0e68452 to
ad7b73b
Compare
andreas-timm
force-pushed
the
feature/release
branch
from
July 4, 2026 13:34
ad7b73b to
a51af90
Compare
andreas-timm
marked this pull request as ready for review
July 4, 2026 23:31
|
🎉 This PR is included in version 0.2.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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
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
CI+Semantic Releaseworkflows, GPG-signed release commits/tags, changelog handling, npmjs trusted publishing and GitHub Packages publish jobs,release:preview/release:publishscripts, and a## Releasingsection in CONTRIBUTING.md.CHANGELOG.mdwith the 0.2.0 section (kept verbatim as release notes by the custom notes plugin) and a backfilled 0.1.3 section.Verification
semantic-releasedry-run from this branch: finds tag0.1.3, analyzes 4 commits (2 feat, 1 fix, 1 test) → next version 0.2.0; preview confirmsCHANGELOG.mdalready contains 0.2.0, so the hand-written notes will be used.release:publish --dry-run: tarball packs cleanly (39 files); npm correctly refuses to overwrite the published 0.1.3 (version bumps only in the CI release job).Repository configuration status
RELEASE_GPG_PRIVATE_KEYsecret setRELEASE_GIT_NAME/RELEASE_GIT_EMAILvariables setsemantic-release.ymlon npmjs.com (verify in npm settings — not checkable via CLI)mainmust allow the workflow'sGITHUB_TOKENto push the release commitMerge note
Merge with a merge commit or fast-forward — do not squash — so commit-analyzer sees the individual
feat:/fix:commits and derives 0.2.0. On merge, the Semantic Release workflow will tag0.2.0, create the signed release commit, publish the GitHub release with the hand-written notes, and publish to npmjs + GitHub Packages.