Merged
Conversation
Contributor
|
I expect a yarn.lock change. Did removing the resolution have no effect on the actual installed version(s) of moment.js? |
Member
Author
Correct @chenba – similar to #18926 I think this resolution had been resolved, or the resolution was noop in the first place. Running |
chenba
approved these changes
May 28, 2025
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.
Because
This pull request
momentIssue that this pull request solves
Closes: FXA-11765
Other information (Optional)
I tested before and after resolution removal: all
momentdependencies are at2.30.1which satisfy the original resolution.