Repository navigation
ci: automate semantic draft releases and npm publishing - #56
Merged
Marcisbee merged 4 commits intoOct 22, 2026
Merged
Conversation
Marcisbee
marked this pull request as ready for review
October 22, 2026 03:04
Marcisbee
marked this pull request as draft
October 22, 2026 09:37
Marcisbee
marked this pull request as ready for review
October 22, 2026 09:40
Marcisbee
deleted the
kode/tdhustwL-prepare-github-actions-for-npm-releases
branch
October 22, 2026 09:50
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.
Pushes to master create or update a draft release using Conventional Commits since the last stable release. Fixes select patch, features select minor, and breaking changes select minor on 0.x or major from 1.0 onward. deno.json remains a version floor, including an explicit opt-in to 1.0.0. Publishing the draft tests and builds the tagged source with that exact version, then publishes to npm using trusted publishing.
PR titles are validated on creation, edits, and updates. Repository squash settings use the PR title and description; AGENTS.md documents the convention for PRs and direct commits. Other types and legacy messages retain a patch fallback. Authors and reviewers remain responsible for identifying breaking changes.
Before the first release, configure npm trusted publishing for Marcisbee/radi and publish-npm.yml; .github/RELEASING.md contains setup and recovery instructions. No npm version or release has been published.
Validation: both GitHub checks pass, covering semantic bump cases, draft lifecycle and escalation, PR-title validation, the package version override and build, npm pack dry run, and all 304 browser tests. Local actionlint passes. A read-only check using Octokit retrieved all 202 existing commits across pages and calculated v0.5.0 with release writes intercepted.