Fix release workflow: use bun install, check version against registry#25
Merged
teallarson merged 1 commit intomainfrom Mar 10, 2026
Merged
Conversation
…istry Replaces npm ci (which required package-lock.json) with bun install, and replaces git-tag-based version checking with a simpler comparison against the published npm version. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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
1 participant
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
npm ci(which requiredpackage-lock.json) withbun install, matching how the repo actually installs dependencies--provenance, noNPM_TOKENneeded)Fixes the release pipeline failure from #23's merge where
npm cifailed with nopackage-lock.json.Test plan
package.jsonversion bump triggers a successful publish🤖 Generated with Claude Code