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

chore(deps): update semantic-release to v17 #51

Merged
merged 1 commit into from
Jan 29, 2020

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 27, 2020

This PR contains the following updates:

Package Type Update Change
semantic-release devDependencies major 16.0.4 -> 17.0.1

Release Notes

semantic-release/semantic-release

v17.0.1

Compare Source

Bug Fixes

v17.0.0

Compare Source

BREAKING CHANGES
  • Require Node.js >= 10.18

Renovate configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever PR becomes conflicted, or if you tick the rebase/retry checkbox below.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by WhiteSource Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 235730c to 351d8e8 Compare January 28, 2020 16:38
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 351d8e8 to b985af6 Compare January 29, 2020 01:17
@sbardian sbardian merged commit 593d8c3 into develop Jan 29, 2020
@renovate renovate bot deleted the renovate/major-semantic-release-monorepo branch January 29, 2020 01:32
@sbardian
Copy link
Owner

🎉 This PR is included in version 8.0.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
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants