Repository navigation
Publish jetdb-wasm to npm on release, and let the npm publishing be tried by hand - #119
Merged
Merged
Conversation
…ried by hand - Add a job that publishes jetdb-wasm to npm after the GitHub release of a tag, beside the crates, through Trusted Publishing with no token stored, unless the version is on npm already - Add a workflow_dispatch trigger that takes a version and runs the npm job alone - Check the version of jetdb-wasm in its Cargo.toml against the tag too Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
- A tag such as v0.4.0-rc.1 made a prerelease on GitHub, but went to npm as latest - Publish a version with a - in it under the next tag Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
- The workflow_dispatch trigger could publish a real version to npm from any branch, with no tests, and npm never lets a version be used again, so a trial could take the place of a release - Stop with the reason when it is run by hand from anything but main, which CI has tested Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
- Any failure of npm view was taken to mean the version is not on npm, so a network or auth failure led on to a publish, and a run by hand with a version already on npm ended green with nothing published - Go on to publish only on E404, stop with the output of npm on any other failure, and fail a run by hand whose version is on npm already Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
- Unlike the other Rust jobs, the npm job built jetdb for Wasm from scratch every time - Add Swatinem/rust-cache Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
- Trusted Publishing is configured on the page of the package on npm, so it cannot be for jetdb-wasm, which is not on npm yet, and the first publish cannot go through this job - Say in the comment of the workflow that the package has to be published once by hand before this job can publish to it Co-Authored-By: Claude Opus 5.5 (1M context) <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
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
🤖 Generated with Claude Code