ci: match v4 tooling packages to v5#23021
Merged
innerdvations merged 2 commits intov4from Feb 28, 2025
Merged
Conversation
innerdvations
added
source: tooling
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Contributor
|
Size Change: 0 B Total Size: 1.33 MB ℹ️ View Unchanged
|
Convly
reviewed
Feb 27, 2025
Member
Convly
left a comment
Convly
left a comment
There was a problem hiding this comment.
Is there any breaking change impacting us in this?
Contributor
Author
There shouldn't be, as long as the monorepo builds. But there does seem to be some sort of conflict with nx in github. I'll take a look later. Update: It was just some cache files that needed to be ignored |
Convly
approved these changes
Feb 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
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.
What does it do?
developbranchWhy is it needed?
to eliminate several packages with vulnerabilities from the yarn.lock; none of them actually affect anything, but it triggers dependabot alerts and vulnerability warnings
How to test it?
Provide information about the environment and the path to verify the behaviour.
Related issue(s)/PR(s)
Let us know if this is related to any issue/pull request