Repository navigation
fix(release): verify installable SDK archives before publishing - #99
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.
Fresh installations cannot start the CLI because importing the compiler eagerly loads the optional
solcpeer. Load it only for compilation, with an actionable missing-peer error; CLI help and artifact loading work without it.The publication workflow now installs and checks the packed archive before publishing that same archive, then checks the exact registry version. CI exercises the packed package, public imports, declarations, installed CLI, missing compiler dependency and real EVM/PQABI compilation. Remove the placeholder registry token configuration so publication uses OIDC. Document the npm trusted publisher identity and prepare 0.14.0-rc.2 on
next; the rc.1 tag failed registry authorization and was not published.Validation:
npm run typecheck,npm test(239 passed, 37 opt-in tests skipped),npm run build, andnpm run test:packagepassed. Actual npm publication remains subject to the configured trusted publisher; no token secret is required.