dcpm icon indicating copy to clipboard operation
dcpm copied to clipboard

chore(deps): update semantic-release monorepo (major)

Open renovate[bot] opened this issue 2 years ago • 0 comments

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@semantic-release/git 7.0.18 -> 10.0.1 age adoption passing confidence
@semantic-release/git 9.0.0 -> 10.0.1 age adoption passing confidence
@semantic-release/npm 5.3.5 -> 12.0.1 age adoption passing confidence
@semantic-release/npm 7.0.5 -> 12.0.1 age adoption passing confidence

Release Notes

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

v9.0.1

Compare Source

Bug Fixes

v9.0.0

Compare Source

chore
  • require Node.js >=10.18 (4016fcc)
BREAKING CHANGES
  • Require Node.js >= 10.18

v8.0.0

Compare Source

Bug Fixes
  • package: update execa to version 4.0.0 (9c1dc67)
  • include deleted files in release commit (f59d20c)
  • package: update aggregate-error to version 2.0.0 (3eb8f60)
  • package: update execa to version 2.0.2 (9404d44)
  • package: update execa to version 3.0.0 (e6af5b4)
  • look for modified fiels to commit only if there files matching the globs (d97c030)
  • update globby to latest version (9e2b2e5)
Features
BREAKING CHANGES
  • Require Node.js >= 10.13
  • Require Git 2.7.1 or higher
  • Require Node.js => 8.15
semantic-release/npm (@​semantic-release/npm)

v12.0.1

Compare Source

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]

v7.1.3

Compare Source

Bug Fixes
  • use NPM_CONFIG_USERCONFIG in get-registry to match auth (#​362) (13200ca)

v7.1.2

Compare Source

Bug Fixes
  • deps: update dependency fs-extra to v10 (80fde1e)

v7.1.1

Compare Source

Bug Fixes
  • deps: update dependency normalize-url to v6 (97ca719)

v7.1.0

Compare Source

Features

v7.0.10

Compare Source

Bug Fixes

v7.0.9

Compare Source

Bug Fixes

v7.0.8

Compare Source

Bug Fixes

v7.0.7

Compare Source

Bug Fixes

v7.0.6

Compare Source

Bug Fixes

v7.0.5

Compare Source

Bug Fixes
  • package: update fs-extra to version 9.0.0 (67a3109)

v7.0.4

Compare Source

Bug Fixes
  • package: update tempy to version 0.5.0 (6ffff19)

v7.0.3

Compare Source

Bug Fixes
  • package: update tempy to version 0.4.0 (4874bf6)

v7.0.2

Compare Source

Bug Fixes
  • package: update normalize-url to version 5.0.0 (a554580)

v7.0.1

Compare Source

Bug Fixes
  • package: update semver to version 7.1.2 (a58b30b)

v7.0.0

Compare Source

chore
  • require Node.js >=10.18 (8140f0f)
BREAKING CHANGES
  • Require Node.js >= 10.18

v6.0.0

Compare Source

Bug Fixes
  • package: update execa to version 4.0.0 (d97dee5)
  • package: update semver to version 6.3.0 (c515862)
  • add dist-tag to publish and add-channel logs (db6ccd2)
  • use correct peerDependencies for semantic-release (8b47e7b)
  • package: pin npm to 6.5.0 (ddab7b7)
  • package: update aggregate-error to version 2.0.0 (df53298)
  • package: update aggregate-error to version 3.0.0 (3e0d5d0)
  • package: update execa to version 3.0.0 (b1780c1)
  • package: update npm to version 6.8.0 (2b0492e)
  • package: update read-pkg to version 5.0.0 (877ce40)
  • package: update vulnerable dependencies (#​185) (a96c6da)
  • skip tarball move if config is cwd (a224497)
  • package: update execa to version 2.0.2 (d2932ba)
  • package: update registry-auth-token to version 4.0.0 (2868b2c)
  • add dist-tag to publish log (2de37a1)
  • Honor NPM_CONFIG_USERCONFIG setting (932ea5e)
  • package: update fs-extra to version 8.0.0 (bf603e5)
  • return false if the npm publish is skipped (4a41228)
  • return false in addChannel if package is not published on npm (5434bab)
Features
  • add addChannel plugin step (fb96126)
  • require Node.js >=10.13 (6426458)
  • require Node.js >=8.15 (4caf538)
  • support nextRelease.channel property in publish step (b8deba7)
BREAKING CHANGES
  • Require Node.js >= 10.13
  • Require Node.js => 8.15

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - 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, check this box

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

renovate[bot] avatar Jan 10 '22 17:01 renovate[bot]