Repository navigation
chore: use published i18n and UI beta.147 packages - #112
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.
Summary
0.1.0-beta.147, updating the pnpm lockfile.Archive comparison / fixtures
Verified both exact versions with
npm viewandnpm pack. Published UI and the previous 24e9f5d0 UI each contain 94 members: onlypackage.jsondiffers (version and development i18n pin). Published kit and vendored kit each contain 37 members: only the package version differs. Runtime code and catalogues are byte-identical; no application API changes or catalogue regeneration needed. All five UI consumer installations are checked against independent member hashes, and fixture integrity is bound to the npm lockfile.npm installation does not imply native publisher/release qualification. The existing native guard continues to reject a registry dependency where it requires an independently approved file intake. No checks or protected approval pins were relaxed.
Verification (rpnpm)
check: lint, formatting, architecture, typecheck, full tests, strict 10-locale i18n/composition/compilation/source gates — PASS.i18n:source: PASS (589 modules).buildandbuild:production: PASS across all workspaces.No publication, release or deployment dispatch. Merge after green PR CI is authorized; the existing main workflow may deploy lab automatically.