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 monorepo (major) #221

Merged
merged 1 commit into from
Jan 18, 2022

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 18, 2022

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@semantic-release/npm 8.0.3 -> 9.0.0 age adoption passing confidence
semantic-release 18.0.1 -> 19.0.2 age adoption passing confidence

Release Notes

semantic-release/npm

v9.0.0

Compare Source

Bug Fixes
  • add preferLocal option to allow execa to use local npm version (#​445) (002439e)
  • updated the peer requirement for semantic-release to the new stable version (575a5a4)
  • updated the peer requirement on semantic-release to a version matching the engines definition of this package (2d1f5f2)
  • upgrade npm dependency to v8 (a12d6e5)
BREAKING CHANGES
  • the minimum required peer of semantic-release has been raised to match the engines.node requirements of this package
  • npm v8 dropped support for node v15, so it is no longer supported in this plugin. this should be low impact since node v15 is already EOL

Co-authored-by: Matt Travi programmer@travi.org

semantic-release/semantic-release

v19.0.2

Compare Source

Bug Fixes
  • npm-plugin: upgraded to the stable version (0eca144)

v19.0.1

Compare Source

Bug Fixes
  • npm-plugin: upgraded to the latest beta version (8097afb)

v19.0.0

Compare Source

Bug Fixes
  • npm-plugin: upgraded to the beta, which upgrades npm to v8 (f634b8c)
  • upgrade marked to resolve ReDos vulnerability (#​2330) (d9e5bc0)
BREAKING CHANGES
  • npm-plugin: @semantic-release/npm has also dropped support for node v15
  • node v15 has been removed from our defined supported versions of node. this was done to upgrade to compatible versions of marked and marked-terminal that resolved the ReDoS vulnerability. removal of support of this node version should be low since it was not an LTS version and has been EOL for several months already.

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 you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, click this checkbox.

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

@renovate renovate bot added the renovate label Jan 18, 2022
@codecov-commenter
Copy link

Codecov Report

Merging #221 (f85992d) into main (dea6d53) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff            @@
##              main      #221   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            1         1           
  Lines           11        11           
  Branches         2         2           
=========================================
  Hits            11        11           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update dea6d53...f85992d. Read the comment docs.

@screendriver screendriver merged commit 90ed316 into main Jan 18, 2022
@screendriver screendriver deleted the renovate/major-semantic-release-monorepo branch January 18, 2022 09:28
@github-actions
Copy link

🎉 This PR is included in version 2.0.7 🎉

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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants