fix(release): restore audio package publishing - #16
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
@web-kits/audio@0.2.0is declared in the repository but absent from npm. The release workflow configures npm without supplying setup-node'sNODE_AUTH_TOKEN, and the package's CLI lacks a Node interpreter header, causing the installedaudioexecutable to fail.This supplies the npm secret under both token names, restores the CLI header, and adds a tarball installation check that imports the library and executes the CLI's version and help commands. CI and releases use Node 24 setup actions; release validation builds only the public package and supports manual retries on main. Recovery instructions and the unreleased 0.2.0 changelog are updated.
Validation: frozen dependency install, full workspace build, typecheck, lint, 55 tests, actionlint, and formatting checks passed. A clean tarball install reproduced the CLI failure before the fix and passes after it. The historical release logs have expired, so its exact failure cannot be confirmed from retained annotations.
Related to #15. Verify npm publication after the repaired workflow runs on main.