Repository navigation
fix: release npm 2.8.0 with React Native, browser and React entry points - #15
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.
The npm package has remained on 2.6.2 while
maingained the/react-native,/browser,/react, and/nuxtentry points. Prepare 2.8.0 with all distributions, declarations, the error monitoring guide, and the source map upload CLI.The release workflow now accepts a manual run from
main, validates the committed version before building, and publishes the exact archive tested in an isolated consumer. This replaces the old post-build version bump and automatic merges intodevelop/master. The existingrelease/X.Y.Ztrigger remains, with an explicit version check. Registry verification checkslatest, exports, and archive integrity after publishing; package visibility is unchanged.Add Kafka as a development dependency for the full build's declarations and React for consumer smoke tests; both remain optional peers. CI skips native install scripts, builds all entry points, and verifies CJS/ESM imports and browser-compatible bundles from the packed archive.
Validation: clean
npm ci --ignore-scripts; all 136 tests; frontend typecheck;tsc --noEmit -p tsconfig.build.json; full build; isolated npm package checks; actionlint; npm audit (0 vulnerabilities).The broad pre-existing
npm run typecheckstill reports errors in legacy examples and test mocks. The production source typecheck and generated declarations pass.