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) #477

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 17, 2021

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@semantic-release/changelog 5.0.1 -> 6.0.3 age adoption passing confidence
@semantic-release/exec 5.0.0 -> 6.0.3 age adoption passing confidence
@semantic-release/git 9.0.1 -> 10.0.1 age adoption passing confidence
@semantic-release/npm 7.1.3 -> 12.0.1 age adoption passing confidence

Release Notes

semantic-release/changelog (@​semantic-release/changelog)

v6.0.3

Compare Source

Bug Fixes

v6.0.2

Compare Source

Bug Fixes

v6.0.1

Compare Source

Bug Fixes

v6.0.0

Compare Source

Features
  • node-version: raised the minimum required version to v14.17 (#​170) (5cf74e4)
BREAKING CHANGES
  • node-version: the minimum required version of node is now v14.17
semantic-release/exec (@​semantic-release/exec)

v6.0.3

Compare Source

Bug Fixes

v6.0.2

Compare Source

Bug Fixes

v6.0.1

Compare Source

Bug Fixes

v6.0.0

Compare Source

Features
  • node-version: raised the minimum required version to v14.17 (#​188) (020eab0)
BREAKING CHANGES
  • node-version: the minimum required version of node is now v14.17
semantic-release/git (@​semantic-release/git)

v10.0.1

Compare Source

Bug Fixes

v10.0.0

Compare Source

Features
  • node-version: raised the minimum required version to v14.17 (7ab65f8)
BREAKING CHANGES
  • node-version: the minimum required version of node is now v14.17
semantic-release/npm (@​semantic-release/npm)

v12.0.1

Compare Source

Bug Fixes
  • deps: update dependency execa to v9 (9ac5ed0)

v12.0.0

Compare Source

Features
  • exports: defined exports to point at ./index.js (9e193c2)
  • node-versions: dropped support for node v18 and v19 (2df962b)
BREAKING CHANGES
  • exports: exports has been defined, which prevents access to private apis (which arent
    intended for consumption anyway)
  • node-versions: node v18 and v19 are no longer supported

v11.0.3

Compare Source

Bug Fixes

even though our existing range allowed anyone to update as soon as the new npm version was available, this will encourage being on a version that does not report the ip vulnerability a bit more forcefully

v11.0.2

Compare Source

Bug Fixes
  • deps: update dependency npm to v10.2.5 (42b5dec)

v11.0.1

Compare Source

Bug Fixes

v11.0.0

Compare Source

Bug Fixes
  • deps: update dependency npm to v10 (819f257)
Features
  • node-versions: raised the minimum required node version to v18.17 and dropped v19 support (6413130)
BREAKING CHANGES
  • node-versions: node v18.17 is now the minimum required version and support for v19 has been dropped

v10.0.6

Compare Source

Bug Fixes

v10.0.5

Compare Source

Bug Fixes

v10.0.4

Compare Source

Bug Fixes

v10.0.3

Compare Source

Bug Fixes

v10.0.2

Compare Source

Bug Fixes

v10.0.1

Compare Source

Bug Fixes

v10.0.0

Compare Source

Bug Fixes
  • aggregate-error: upgraded to the latest version (7285e05)
  • deps: upgraded npm to v9 (2a79f80)
  • execa: upgraded to the latest version (7c74660)
  • normalize-url: upgraded to the latest version (b55bb01)
  • remove support for legacy auth (51ab3c8)
  • tempy: upgraded to the latest version of tempy (f1992a5)
Code Refactoring
  • esm: converted the package to esm (2d8ff15)
Features
  • node-versions: dropped support for node versions below v18 (aff3574)
  • semantic-release-peer: raised the minimum peer requirement to the first version that supports loading esm plugins (22e70ad)
BREAKING CHANGES
  • deps: the direct dependency on npm has been upgraded to v9. details of breaking changes
    can be found at https://github.com/npm/cli/releases/tag/v9.0.0
  • semantic-release-peer: the required version of semantic-release has been
    raised to v20.1.0 in order to support loading of ESM plugins
  • aggregate-error: due to the aggregate-error upgrade, thrown errors are no longer iterable, but instead list the errors under an errors property
  • legacy authentication using NPM_USERNAME and NPM_PASSWORD is no longer supported. Use NPM_TOKEN instead.
  • node-versions: node v18 is now the minimum required node version
  • esm: @semantic-release/npm is now a native ES Module. It
    has named exports for each plugin hook (verifyConditions, prepare,
    publish, addChannel)

v9.0.2

Compare Source

Bug Fixes
  • deps: update dependency fs-extra to v11 (7157d76)
  • deps: update dependency npm to v9 (28265ec)
  • deps: update dependency registry-auth-token to v5 (187671f)
  • revert): "fix(deps: update dependency npm to v9" (#​561) (c28a848)

v9.0.1

Compare Source

Bug Fixes

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 [email protected]

v8.0.3

Compare Source

Reverts

v8.0.2

Compare Source

Bug Fixes

v8.0.1

Compare Source

Bug Fixes

v8.0.0

Compare Source

Features
BREAKING CHANGES
  • node-version: the minimum required version of node is now v14.17

Co-authored-by: Matt Travi [email protected]


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 10 times, most recently from 3243ae7 to 5c7c5ac Compare September 27, 2021 20:12
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 9 times, most recently from bfbde1c to 0b42ed2 Compare October 4, 2021 19:59
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 10 times, most recently from fe63786 to 222d7af Compare October 11, 2021 22:47
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 222d7af to fc5a746 Compare October 12, 2021 20:32
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 11 times, most recently from e43c281 to b2d3314 Compare March 6, 2022 07:39
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 4 times, most recently from 9745a2f to 8f80a60 Compare March 9, 2022 16:57
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 8f80a60 to 3b4fb62 Compare September 25, 2022 12:32
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 3b4fb62 to 49aff5b Compare November 20, 2022 16:47
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 49aff5b to ccf5f52 Compare March 16, 2023 13:25
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from ccf5f52 to 60ec76c Compare March 24, 2023 15:36
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 60ec76c to 6c2144b Compare April 17, 2023 09:40
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 6c2144b to 53f4bfe Compare June 14, 2023 12:21
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 53f4bfe to 9a2924c Compare August 19, 2023 16:40
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from e3b882d to f2adf06 Compare September 15, 2023 21:32
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from f2adf06 to f8b89a4 Compare November 3, 2023 00:10
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from f8b89a4 to a7fa5df Compare December 7, 2023 18:16
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from a7fa5df to 89a91c4 Compare March 2, 2024 20:18
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 89a91c4 to d531f18 Compare March 16, 2024 06:22
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from d531f18 to 16a729b Compare May 9, 2024 17:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants