Repository navigation
ci: add CI checks and release-please releases - #4
Merged
Merged
Conversation
CI runs `npm run check` (typecheck, build, tests, pack dry-run) on Node 20, 22, and 24 for every pull request and push to main. The publish workflow now also runs release-please on pushes to main. It keeps a release PR open; merging it tags vX.Y.Z, creates the GitHub Release, and publishes to npm in the same run. Hand-made releases still publish through the `release` event. The file name stays the same so npm trusted publishing can be bound to it. The manifest starts at 0.2.1, which was released by hand, and CHANGELOG.md is seeded with 0.2.0 and 0.2.1. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.
Summary
.github/workflows/ci.yml):npm run check(typecheck, build, tests,npm pack --dry-run) on Node 20/22/24 for every PR and push tomain..github/workflows/publish.yml, now named "Release"): on pushes tomain, release-please keeps a release PR open. Merging it bumpspackage.json/package-lock.json, updatesCHANGELOG.md, tagsvX.Y.Z, creates the GitHub Release, and publishes to npm in the same run.releaseevent. Releases created by release-please useGITHUB_TOKENand do not fire that event, so nothing is published twice.publish.ymlso npm trusted publishing can be bound to it.workflow_dispatchis a dry run by default; uncheckingdry-runnow actually publishes (useful as a fallback).0.2.1, which was released by hand, andCHANGELOG.mdis seeded with 0.2.0 and 0.2.1.featand breaking changes bump the minor while below 1.0.checkout@v7/setup-node@v7/release-please-action@v5(Node 24 runtime, removes the Node 20 deprecation warning).Needed once in the repository settings
Notes
GITHUB_TOKENdo not trigger CI. The release PR only touches version/changelog files, and the publish job runsnpm run checkagain before publishing.Test plan
npm run checkpasses locallyactionlintpasses on both workflowsci:commits since v0.2.1)🤖 Generated with Claude Code