Skip to content

feat: release from CI with auto-incrementing versions - #260

Merged
jcary741 merged 3 commits into
mainfrom
ci-auto-release
Oct 27, 2026
Merged

jcary741 merged 3 commits into
mainfrom
ci-auto-release

Conversation

@jcary741

Copy link
Copy Markdown
Contributor

Releases publish to npm automatically from main via Trusted Publishing, replacing tag-triggered publishing. Versions come from the PR title's Conventional Commit prefix (fix: patch, feat: minor, feat!: major; other prefixes don't release).

Running the workflow manually on a branch publishes a prerelease under the prerelease dist-tag.

Also:

  • Docs still deploy to GitHub Pages, now only after a real (latest) release.
  • package.json stays at 2.25.0, the version released by hand.
  • Bumps actions/checkout to v5 and actions/setup-node to v6 (removes the Node 20 deprecation warnings).

@jcary741
jcary741 requested a review from a team as a code owner October 20, 2026 18:41
@ox-security

ox-security Bot commented Oct 21, 2026

Copy link
Copy Markdown

OX Security Logo

Internal scan identifier: 844ece5a-82a9-40c0-88da-20c1cc5451d5.

We are sorry, but we were unable to perform a scan on your repository at this time. Please try again later. Contact OX Security support if the issue persists.

@jcary741
jcary741 merged commit 885fa3c into main Oct 27, 2026
5 checks passed
@jcary741
jcary741 deleted the ci-auto-release branch October 27, 2026 18:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants