Skip to content

Conversation

@renovate
Copy link

@renovate renovate bot commented May 8, 2020

This PR contains the following updates:

Package Change Age Confidence
@semantic-release/changelog 3.0.2 -> 6.0.3 age confidence
@semantic-release/git 7.0.8 -> 10.0.1 age confidence
@semantic-release/npm 5.1.4 -> 13.1.2 age 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

v5.0.1

Compare Source

Bug Fixes
  • package: update fs-extra to version 9.0.0 (997fe15)

v5.0.0

Compare Source

chore
  • require Node.js >=10.18 (5ffdf49)
BREAKING CHANGES
  • Require Node.js >= 10.18

v4.0.0

Compare Source

Features
  • require Node.js >=10.13 (1f483af)
BREAKING CHANGES
  • Require Node.js >= 10.13

v3.0.6

Compare Source

Bug Fixes
  • use correct peerDependencies for semantic-release (d36ee06)

v3.0.5

Compare Source

Bug Fixes

v3.0.4

Compare Source

Bug Fixes
  • package: update fs-extra to version 8.0.0 (50ed752)

v3.0.3

Compare Source

Bug Fixes
  • package: update aggregate-error to version 3.0.0 (50789ef)
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
  • require Node.js >=10.13 (81955b8)
  • require Node.js >=8.15 (15356b1)
  • support branch parameter from semantic-release@​16.0.0 (02b1f6d)
BREAKING CHANGES
  • Require Node.js >= 10.13
  • Require Git 2.7.1 or higher
  • Require Node.js => 8.15

v7.0.18

Compare Source

Bug Fixes
  • use correct debug scope (3323aac)

v7.0.17

Compare Source

Bug Fixes
  • package: update execa to version 3.2.0 (5132713)
  • require Node.js >=8.16 (7c9eb9a)

v7.0.16

Compare Source

Bug Fixes
  • package: update globby to version 10.0.0 (a93b846)

v7.0.15

Compare Source

Bug Fixes
  • package: update dir-glob to version 3.0.0 (2819d3b)

v7.0.14

Compare Source

Bug Fixes

v7.0.13

Compare Source

Bug Fixes
  • package: update execa to version 2.0.0 (39c4fd5)

v7.0.12

Compare Source

Bug Fixes
  • package: update fs-extra to version 8.0.0 (712d684)

v7.0.11

Compare Source

Bug Fixes
  • package: update aggregate-error to version 3.0.0 (239eba1)

v7.0.10

Compare Source

Bug Fixes
  • package: update micromatch to version 4.0.0 (94e9e12)

v7.0.9

Compare Source

Bug Fixes
  • package: update p-reduce to version 2.0.0 (7ee4af9)
semantic-release/npm (@​semantic-release/npm)

v13.1.2

Compare Source

Bug Fixes

v13.1.1

Compare Source

Bug Fixes
  • publish-dry-run: temporarily remove the addition of dry-running the publish step (30bd176)

v13.1.0

Compare Source

Features
  • trusted-publishing: verify auth, considering OIDC vs tokens from various registries (e3319f1), closes #​958
  • trusted-publishing: refine the messages for related errors (316ce21), closes #​958
  • trusted-publishing: make request to verify if OIDC token exchange can succeed (c80ecb0), closes #​958
  • trusted-publishing: pass id-token as bearer header for github actions (d83b727), closes #​958
  • trusted-publishing: pass id-token as bearer header for gitlab pipelines (6d1c3cf), closes #​958
  • trusted-publishing: handle failure to retrieve id-token in the context of github actions (b673257), closes #​958
  • auth-error: update messaging for auth failure to be less token specific (e24967d)
  • auth: attempt a dry-run publish to determine auth status (841dc67)
Bug Fixes
  • trusted-publishing: uri encode the package name for the token exchange request (3dd95d0), closes #​958
  • auth: throw appropriate error when auth context fails to enable publishing (f5c8d85)
  • auth: throw error if dry-run publish determines lack of auth (8f88e9d)
  • verify-auth: enable the publish dry-run to work for projects publishing from a sub-directory (e7d684c)

v13.0.0

Compare Source

Features
  • node-versions: drop support for node versions v20, v21, and v23
  • node-versions: raise the minimum node version requirement for the v24 range (935439e)
Bug Fixes
BREAKING CHANGES
  • node-versions: the minimum node version for the v24 range is now v24.10.0
  • deps: a minimum of node v22.14 is now required

v12.0.2

Compare Source

Bug Fixes

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 programmer@travi.org

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 programmer@travi.org

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

v5.3.5

Compare Source

Bug Fixes
  • include version in npm release URL (827fcb3)

v5.3.4

Compare Source

Bug Fixes
  • log the output of npm whoami command (cd1ecaa)

v5.3.3

Compare Source

Bug Fixes
  • avoid adding unnecessary new line to .npmrc (6189ee7)
  • log the path of existing .npmrc files (a0120d2)

v5.3.2

Compare Source

Bug Fixes
  • preserve config in both home and local .npmrc (de677ea)

v5.3.1

Compare Source

Bug Fixes
  • package: update execa to version 3.2.0 (7db019f)
  • require Node.js >=8.16 (fce3a67)

v5.3.0

Compare Source

Features
  • preserve local .npmrc file (8726eff)

v5.2.0

Compare Source

Features
  • allow to configure the registry via NPM_CONFIG_REGISTRY (0126704)

v5.1.15

Compare Source

Bug Fixes

v5.1.14

Compare Source

Bug Fixes
  • package: update execa to version 2.0.2 (2a45e25)

v5.1.13

Compare Source

Bug Fixes

v5.1.12

Compare Source

Bug Fixes
  • skip tarball move if config is cwd (a457fdc)

v5.1.11

Compare Source

Bug Fixes
  • package: update execa to version 2.0.0 (9498e21)

v5.1.10

Compare Source

Bug Fixes
  • package: update registry-auth-token to version 4.0.0 (9a6176d)

v5.1.9

Compare Source

Bug Fixes
  • Honor NPM_CONFIG_USERCONFIG setting (1395b18)

v5.1.8

Compare Source

Bug Fixes
  • package: update fs-extra to version 8.0.0 (8288c24)

v5.1.7

Compare Source

Bug Fixes
  • package: update aggregate-error to version 3.0.0 (46ec5ee)

v5.1.6

Compare Source

Bug Fixes
  • package: update read-pkg to version 5.0.0 (d03aff2)

v5.1.5

Compare Source

Bug Fixes
  • package: update npm to version 6.8.0 (62b27c5)

Configuration

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

🚦 Automerge: Enabled.

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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from cb2a42f to 04b32e4 Compare June 30, 2020 15:03
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 04b32e4 to 676b24d Compare October 28, 2020 07:04
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 676b24d to 9db3cca Compare November 27, 2020 20:02
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 9db3cca to e8131c8 Compare December 9, 2020 18:57
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from e8131c8 to 59edf4d Compare January 23, 2021 14:54
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 59edf4d to a2d207c Compare April 26, 2021 14:47
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from a2d207c to 2341e96 Compare May 9, 2021 21:28
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 2341e96 to 1da9321 Compare October 18, 2021 18:42
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 1da9321 to a9f2cb6 Compare March 7, 2022 15:14
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from a9f2cb6 to 490a19a Compare September 25, 2022 15:56
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 490a19a to 8544486 Compare March 16, 2023 11:17
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 8544486 to c3be306 Compare March 25, 2023 00:16
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from c3be306 to 1affc4c Compare April 17, 2023 13:51
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 1affc4c to d9b81bf Compare June 9, 2023 22:26
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from d9b81bf to 7ed93f3 Compare August 19, 2023 19:18
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 8b7e652 to 9284640 Compare September 15, 2023 21:14
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 9284640 to c435740 Compare November 2, 2023 23:00
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from c435740 to 808c95b Compare December 7, 2023 20:10
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 808c95b to a6c2da7 Compare March 1, 2024 22:55
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from a6c2da7 to 0f2fdda Compare March 16, 2024 04:29
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 519878e to eb0705a Compare April 9, 2024 23:17
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 5dc7f63 to 4f4aa85 Compare May 11, 2024 00:07
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 4f4aa85 to 8aa15fc Compare May 31, 2024 23:43
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 8aa15fc to fca1c4d Compare June 26, 2025 18:50
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 1a16b84 to c5e454f Compare August 13, 2025 12:34
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from c5e454f to 02b1fc9 Compare August 19, 2025 20:38
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 02b1fc9 to 3d1a2f7 Compare August 31, 2025 12:03
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 3d1a2f7 to 95e1355 Compare September 25, 2025 17:38
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 860f1bc to df9ac91 Compare October 19, 2025 18:03
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from df9ac91 to 1876f8d Compare November 10, 2025 22:53
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 1876f8d to 80b1d13 Compare November 14, 2025 23:08
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.

1 participant