Repository navigation
chore: prepare stable 0.2.2 release - #44
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
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.
Changes
Prepare stable 0.2.2 with matching package and lockfile versions. The release includes the Debian Bullseye download fix, Linux ARM64 glibc prebuilds, the Windows ARM64 OpenSSL build fix, and the audited libdatachannel v0.24.6 pin. Linux ARM64 glibc prebuilds require this new package version; ARM64 musl retains source-build fallback.
Manual Release dispatch now validates all seven archives without uploading assets or publishing npm. Publishing a GitHub release builds and validates again, refuses an existing npm version or release asset, then uploads checksums and publishes through npm trusted publishing. Published Install runs automatically only after publication and tests an exact package version with source fallback disabled.
Release validation checks architecture, static OpenSSL selection and runtime dependencies, glibc 2.31 compatibility, archive integrity, mismatched target rejection, packaged CJS/ESM installation, and data-channel exchange. A real ARM64 Alpine job validates source fallback.
Validation