ci: release publish workflow, PR-title validation, and commit conventions#80
Merged
Conversation
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.
What
Bundles the release automation (Fase 4) and the guardrails that keep the auto-generated changelog clean.
Changes
.github/workflows/publish.yml— publishes to npm onv*tags via OIDC trusted publishing (noNPM_TOKENsecret) with build provenance. Verifies the tag matchespackage.jsonversion before publishing..github/workflows/pr-title.yml— validates PR titles are Conventional Commits. Since PRs are squash-merged, the PR title becomes the changelog entry; commitlint only checks local commits, so this closes that gap.CONTRIBUTING.md— documents that PR titles must be conventional, thatCHANGELOG.mdis never hand-edited (generated at release time), and that pushing a tag auto-publishes to npm via CI.Repo setting (applied, not part of the diff)
Merges are now squash-only (merge-commit and rebase disabled), so each PR lands as one conventional commit → one clean changelog entry.
Required setup on npmjs.com (one-time, before the next tag)
mint-dspackage → Settings → Trusted Publisher → add a GitHub Actions publisher:nujovich/mintpublish.ymlWithout this, the publish step fails with an auth error. No repo secret needed.
Testing
publish.ymlruns only on tag push — first real exercise is the next release tag after the trusted publisher is configured.pr-title.ymlruns on this PR and validates its own (conventional) title.