Skip to content

fix: resolve release tarball without parsing npm lifecycle output - #17

Merged
lodystage[bot] merged 1 commit into
mainfrom
fix/1171-release-packaging
Oct 22, 2026
Merged

lodystage[bot] merged 1 commit into
mainfrom
fix/1171-release-packaging

Conversation

@lodystage

@lodystage lodystage Bot commented Oct 22, 2026

Copy link
Copy Markdown
Contributor

Fix the 1.17.1 release packaging step: npm lifecycle output can appear in stdout even when requesting JSON, so do not parse that output to find the tarball. Use the known package name and validated version instead. Allow a distinct build retry tag while preserving the original release tag and npm version.

Validation: downloaded the successful iOS and Android artifacts from run 39811033804, assembled a real 17.8 MB npm tarball locally, and passed the release verifier against both native libraries, generated bindings, JS entry points, declarations, and locked core versions. actionlint and diff checks passed.

@lodystage
lodystage Bot force-pushed the fix/1171-release-packaging branch 2 times, most recently from 2e36ba4 to 1cab644 Compare October 22, 2026 16:31
@lodystage
lodystage Bot merged commit 6c44856 into main Oct 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant