Repository navigation
fix(opp-bundles): publish the cargo crate before npm and report every publish failure - #621
Merged
Merged
Conversation
… publish failure The bundler published the two npm packages first and the cargo crate last, and the first throw ended the run. The two registries share no credential: the crate publishes to CodeArtifact over the OIDC-minted registry token, the npm packages publish to npmjs.org with NPM_TOKEN. Since 2026-09-14 the npm publish fails (E404 on PUT, an auth failure), and every master run since has died before reaching the cargo step, so wire-opp-solana-models never advanced past 1.0.50 even though nothing on the cargo side was broken. Consumers of the SYNDICATE_LIQ / LIQ_YIELD / DESYNDICATE_LIQ types added in #609 (wire-solana #523, wire-tools-ts #98) are blocked on a credential the crate never uses. handlePublish now publishes the cargo crate first, then each npm package, runs every publish to completion, and throws one error carrying all the failures as its cause. A re-run after the npm side is repaired heals npm without re-publishing the crate: publishCargoCrate already treats a duplicate version as success. Verified: tsc -b clean; protobuf-bundler jest 34/34. Co-Authored-By: Claude Fable 5.1 <[email protected]> Claude-Session: https://claude.ai/code/session_01CNDguHHWTwn1UBejDiTAGa Change-Id: Ie6974d6220e088f4d711ed01d718fb7019f19481
jglanz
approved these changes
Sep 16, 2026
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.
Problem
The OPP Bundles workflow publishes three bundles from one bundler run:
@wireio/opp-typescript-modelsand@wireio/opp-solidity-modelsto npmjs.org withNPM_TOKEN, andwire-opp-solana-modelsto CodeArtifact over the OIDC-minted registry token.handlePublishran the npm publishes first and the cargo publish last, and the first throw ended the run.Since 2026-09-14 the npm publish fails (
E404onPUT, an auth failure on the token). Every master run since, including the one #609 triggered, died before the cargo step, sowire-opp-solana-modelsnever advanced past 1.0.50 even though the cargo side was never broken. The consumers of theSYNDICATE_LIQ/LIQ_YIELD/DESYNDICATE_LIQtypes from #609 (wire-solana #523, wire-tools-ts #98) are blocked on a credential the crate does not use.Change
handlePublishpublishes the cargo crate first, then each npm package, runs every publish to completion, and throws one error carrying all the failures as itscause. A re-run after the npm side is repaired heals npm without re-publishing the crate:publishCargoCratealready treats a duplicate version as success.Verification
tsc -b: cleanprotobuf-bundlerjest: 34/34🤖 Generated with Claude Code
https://claude.ai/code/session_01CNDguHHWTwn1UBejDiTAGa