feat!: establish v7 locale and conversion contracts - #2441
Merged
Conversation
Prepare v7 with canonical locale identifiers, typed resolution, and immutable runtime options. Validate custom locales automatically and expose strict or compose range behavior explicitly. Rename ee-EE to et-EE and np-NP to ne-NP with IANA-backed locale-code validation. Add capability metadata and harden package, runtime, CLI, release, and docs verification. Repair Pages deployment and make the docs demo lazily load the v7 per-locale entry points. Update migration guidance, examples, generated references, tests, and dependency tooling. BREAKING CHANGE: Remove the ee-EE and np-NP entry points and locale codes. Use et-EE and ne-NP instead. Conversion now defaults to strict range validation at each locale form's verified ceiling. Use rangeMode compose to retain legacy recursive composition. Public custom locale setup now validates the locale contract.
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2441 +/- ##
==========================================
Coverage 100.00% 100.00%
==========================================
Files 142 144 +2
Lines 2158 2281 +123
Branches 448 495 +47
==========================================
+ Hits 2158 2281 +123 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Remove the direct network-to-file flow flagged by CodeQL. Validate local registry input, prevent rollback, and write the snapshot atomically. Document the separate download and reviewed import procedure.
Merged
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
3 participants
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 v7 with canonical locale identifiers, typed resolution, and immutable runtime options.
Validate custom locales automatically and expose strict or compose range behavior explicitly.
Rename ee-EE to et-EE and np-NP to ne-NP with IANA-backed locale-code validation.
Add capability metadata and harden package, runtime, CLI, release, and docs verification.
Repair Pages deployment and make the docs demo lazily load the v7 per-locale entry points.
Update migration guidance, examples, generated references, tests, and dependency tooling.
BREAKING CHANGE: Remove the ee-EE and np-NP entry points and locale codes. Use et-EE and ne-NP instead.
Conversion now defaults to strict range validation at each locale form's verified ceiling. Use rangeMode compose to retain legacy recursive composition. Public custom locale setup now validates the locale contract.