Fix lockfile to resolve packages to public npm registry#2428
Merged
Conversation
These packages were inadvertently resolved to the private Cloudsmith mirror we maintain, so the npm installation failed unless you had a suitable auth token configured.
ivomurrell
requested review from
a team and
ft-dependency-auto-merger
as code owners
Member
|
To prevent this happening again, we should add a |
Contributor
Author
@joelcarr i'd need to revert #2419 to do that. not sure what the best approach is (we haven't looked into our approach in platforms yet) so maybe we just merge this fix for now? |
joelcarr
approved these changes
May 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
2 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.
These packages were inadvertently resolved to the private Cloudsmith mirror we maintain, so the npm installation failed unless you had a suitable auth token configured. This was blocking some of our engineers who haven't configured Cloudsmith yet and also would have caused users outside of the FT to be unable to install the repository.