Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Upgrade semantic-release from 17.1.2 to 17.2.0 #154

Merged
merged 2 commits into from
Oct 18, 2020

Conversation

snyk-bot
Copy link

Snyk has created this PR to upgrade semantic-release from 17.1.2 to 17.2.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 1 version ahead of your current version.
  • The recommended version was released a day ago, on 2020-10-11.
Release notes
Package name: semantic-release from semantic-release GitHub release notes
Commit messages
Package name: semantic-release
  • b8fb35c feat: throw an Error if package.json has duplicate "repository" key (#1656)
  • 18e35b2 docs: reorder default plugins list (#1650)
  • e35e5bb docs(contributing): fix commit message examples (#1648)
  • 311c465 docs(README): welcome @travi, add alumni section

Compare


Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@randytarampi randytarampi merged commit 79a2e9a into master Oct 18, 2020
@randytarampi randytarampi deleted the snyk-upgrade-26c358b58f3991946b1599377a18eb8d branch October 18, 2020 21:16
@randytarampi
Copy link
Owner

🎉 This PR is included in version 3.0.14 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants