Repository navigation
chore: prepare schema-typed 2.4.3 - #90
Merged
Merged
Conversation
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. |
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.
Prepare 2.4.3 with the merged asynchronous validation failure propagation fix (#88) and lodash dependency update (#89).
The publish job currently uses Node 12, while the locked Mocha 10 dependency requires Node 14 or newer. Use Node 22 for publication, install the reviewed lockfile with
npm ci, and include Node 22 in the existing CI matrix.Validation: isolated Node 22.22.3
npm ciandnpm run prepublishOnlypass (lint, 174 tests, CJS/ESM builds). All 42 generated declarations are byte-identical to the qualified #88 build. The packed 2.4.3 archive contains the exact built files and was inspected locally.Publication remains triggered by a separate version tag. This PR prepares the reviewed package and release workflow.