Repository navigation
chore(repo): Remove socket registry from yarn lock - #490
Merged
Merged
Conversation
Lms24
requested review from
a team,
cleptric,
mjq and
nsdeschenes
as code owners
July 13, 2026 09:50
Semver Impact of This PR🟢 Patch (bug fixes) 📋 Changelog PreviewThis is how your changes will appear in the changelog. New Features ✨Attributes
Other
Internal Changes 🔧
🤖 This preview updates automatically when you update the PR. |
buenaflor
approved these changes
Jul 13, 2026
andreiborza
approved these changes
Jul 13, 2026
cleptric
approved these changes
Jul 13, 2026
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.
It seems like somehow, the Socket package registry slipped into this repo's yarn lock and retargeted the installation sources of a few packages. We're trialing this registry at the moment but I confirmed internally that this must have been an accident and we should still use the official NPM registry at this time. The Socket one caused a lot of installation flakes (403 errors during package installation in CI).
This PR removes the URLs pointing to the Socket registry in favour of the NPM registry.