Repository navigation
Fix npm publishing of the verified tarball - #5
Merged
Merged
Conversation
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.
The first tagged release passed verification, then npm treated
release/fluiddb-fluiddb-1.0.0-next.5.tgzas GitHub shorthand and attempted an SSH clone. Prefix the downloaded artifact path with./so npm publishes the verified local tarball.Use
1.0.0-next.6for the retry and retain the failednext.5tag. The SDK implementation is unchanged from #4.Validation: built the new single-package artifact, copied it into a clean temporary directory without a checkout, and ran the exact fixed publish command with
--dry-run. npm selected the correct tarball and version.bun run release:checkand./ref-checkpass; CI runs the full package, Worker and real-adapter checks again.