ten-thousand-hammers/Changelog Release

Compute the next CalVer version, insert the release notes into CHANGELOG.md, clean up consumed fragments, commit and tag the release, and create a GitHub Release.

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Stale
License
None
namedescriptionrequireddefault
changesRelease notes body (e.g. the merged "Unreleased" section).yes
versionVersion to release. Leave empty to compute the next CalVer version from tags on main.no""
changelog-filePath to the cumulative changelog file to insert into.noCHANGELOG.md
insert-line1-based line number in the changelog file to insert the new release entry at.no7
fragments-dirDirectory of consumed per-PR fragments to delete.nochangelog
combined-fileTransient merged changelog file to delete.noCHANGES_COMBINED.md
version-fileOptional file to write the version string to (e.g. config/version). Leave empty to skip.no""
extra-addExtra space-separated paths to include in the release commit.no""
commit-message-prefixPrefix for the release commit message.nochore: Release
skip-ciAppend "[skip ci]" to the commit message.notrue
tagCreate and push a git tag for the version.notrue
create-github-releaseCreate a GitHub Release for the version.notrue
make-latestMark the GitHub Release as the latest.notrue
prereleaseMark the GitHub Release as a prerelease.nofalse
tokenToken used to create the GitHub Release.no${{ github.token }}
namedescription
versionThe version that was released.
releasedWhether a GitHub Release was created.