chore(deps): use published connect-ui npm release - #45
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
1 participant
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.
Pin
@qrlwallet/connect-uito npm version 0.2.1 and use its registry URL in the lockfile now that publication is complete. The package archive and integrity match the previously pinned GitHub release exactly.Validation: clean
npm ci --ignore-scripts, package formatting, frontend tests (10), andnpm run build(including type checks) passed.npm run lintpassed with zero warnings. Every generated frontend file matches the deployed release byte-for-byte, so this change needs no runtime rollout. The existing dependency audit findings and bundle-size warning remain unchanged.