chore: update semantic-release #1040
Merged
Conversation
This file contains 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
SimenB
commented
Jan 31, 2022
package.json
Outdated
| @@ -159,7 +159,9 @@ | |||
| ] | |||
| }, | |||
| "resolutions": { | |||
| "@typescript-eslint/experimental-utils": "^5.0.0" | |||
| "@typescript-eslint/experimental-utils": "^5.0.0", | |||
| "fsevents/node-gyp": "^7.0.0", | |||
There was a problem hiding this comment.
added this as well to avoid yarn choosing latest
This was referenced Jan 31, 2022
|
馃帀 This PR is included in version 26.1.0-next.1 馃帀 The release is available on: Your semantic-release bot 馃摝馃殌 |
|
馃帀 This PR is included in version 26.1.0 馃帀 The release is available on: Your semantic-release bot 馃摝馃殌 |
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.
We need to force npm to be on v7 due to some change they've made which uses wildcards for all dependencies, leading to pulling in incompatible versions in yarn since they don't respect
bundleDependencies.I've reported this to yarn (discord, so no link), and I think they're gonna fix it 馃檪 But this fixes a "vulnerability" (which, as always, is complete bullshit, but it is what it is)