sasjs-release
@sasjs/release
@sasjs/release is the org's release tool: one file (release.mjs), zero dependencies, bin: sasjs-release. It classifies conventional commits, computes the version, writes the notes, creates the tag and the host release, and attaches assets. It does not publish to npm - that stays a separate step, in the workflow file the package's trusted publisher is registered against.
It replaced semantic-release for two reasons: semantic-release depends on npm as a package, and npm's bundled tree puts advisories in the dev dependencies that no override can clear; and its GitHub plugin uploads the assets it finds while saying nothing about the ones it does not, which is how a release was published with no files on it while every check stayed green.
This skill covers the tool and the pipeline around it. The cross-repo release order (library, then publish, then consumer pin) belongs to the org's release process, and the CLI's own workflows are in sasjs-cli.
Run npx sasjs-release --help for the flags available; the tool gains modes between releases.
The model
- The version is the tag. Nothing writes a version into
package.jsonin the repository;--prepare-publishstamps it into the working tree for the publish, and the tree is thrown away. - The notes are the commits the tag covers. There is no
CHANGELOG.mdwriter; the release page is the changelog. - Host-neutral. GitHub, Gitea and GitLab over plain
https.--host nonedoes the git work only. - Idempotent.
--tag,--push-tagand--releasecan be re-run: an existing tag at HEAD is reused, and an existing release is found rather than duplicated.