fix: remove the recent yarn engine requirement #71
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
… package managers, too)
lisli1
approved these changes
Jul 19, 2019
karanbirsingh
approved these changes
Jul 19, 2019
4 tasks
dbjorge
added a commit
that referenced
this pull request
Jul 19, 2019
Bumps all devDependencies up to latest versions. Leaving bumps of non-dev-dependencies @types/sarif and axe-core for a separate PR since they'll require test updates to check for input format changes. (This should be a chore: and not a fix:, but I used the wrong tag in the last fix: PR's merge commit [the GitHub behavior where it doesn't use the PR title for the merge commit title if there's only one commit in the PR strikes again], so using fix here to artifically force a semantic-release that includes #71 )
|
🎉 This PR is included in version 2.0.2 🎉 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.
Description of changes
Previously, we set an engine requirement of
"yarn": "^1.15.1", which forced prospective consumers to use pretty recent yarn versions in their consuming projects even though we don't actually need any recent yarn features. We aren't doing anything special in our package.json; we don't need to require any single specific package manager (npm, yarn, etc are fine to consume the project with), so this just removes the package manager engine requirement outright.Pull request checklist
fix:,feat:, etc, and is suitable for user-facing release notes)BREAKING CHANGE:yarn precheckin