Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Oct 1, 2023

This PR contains the following updates:

Package Change Age Confidence
@semantic-release/npm 10.0.413.1.3 age confidence
@semantic-release/release-notes-generator 11.0.414.1.0 age confidence
semantic-release 21.0.725.0.2 age confidence

Release Notes

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

v13.1.3

Compare Source

Bug Fixes

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
semantic-release/release-notes-generator (@​semantic-release/release-notes-generator)

v14.1.0

Compare Source

Features

v14.0.3

Compare Source

Bug Fixes

v14.0.2

Compare Source

Bug Fixes

v14.0.1

Compare Source

Bug Fixes

v14.0.0

Compare Source

Features
BREAKING CHANGES
  • by supporting the latest major versions of conventional-changelog packages, we are dropping support for previous major versions of those packages due to the breaking changes between majors. this only impacts your project if you are installing alongside semantic-release, so updating those packages to latest version should be the only change you need for this update. no action should be necessary if you are using default semantic-release config

v13.0.0

Compare Source

Features
  • exports: defined exports to point at ./index.js (5655b18)
  • node-versions: dropped support for node v18 and v19 (e65959a)
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

v12.1.0

Compare Source

Features

v12.0.1

Compare Source

Bug Fixes

v12.0.0

Compare Source

Bug Fixes
  • deps: update dependency conventional-changlog-writer to v7 (4fe3563)
Features
  • conventional-changelog-presets: supported new preset format (a681671)
  • node-versions: raised the minimum node version to v18.17 and dropped v19 support (9c4e5f5)
BREAKING CHANGES
  • node-versions: the minimum required node version is now v18.17, v19 support has been dropped, and the minimum required in the v20 range is v20.6.1
  • conventional-changelog-presets: the new preset format is a breaking change when compared to the previous preset format. updating to support the new format means that the old preset format is no longer supported. update your preset to the latest version to maintain compatibility

v11.0.7

Compare Source

Bug Fixes
  • deps: update dependency conventional-commits-filter to v4 (a347fa6)

v11.0.6

Compare Source

Reverts
  • Revert "chore(deps): update dependency conventional-changelog-atom to v4 (#​509)" (e6b939a), closes #​509
  • Revert "chore(deps): update dependency conventional-changelog-ember to v4 (#​511)" (1f6fa69), closes #​511
  • Revert "chore(deps): update dependency conventional-changelog-conventionalcommits to v7 (#​510)" (9793686), closes #​510
  • Revert "chore(deps): update dependency conventional-changelog-eslint to v5 (#​512)" (a74f93d), closes #​512
  • Revert "chore(deps): update dependency conventional-changelog-express to v4 (#​513)" (a84e7ed), closes #​513

v11.0.5

Compare Source

Bug Fixes
  • deps: update dependency conventional-commits-parser to v5 (#​508) (45f893f)
semantic-release/semantic-release (semantic-release)

v25.0.2

Compare Source

Bug Fixes

v25.0.1

Compare Source

Bug Fixes

v25.0.0

Compare Source

Bug Fixes
  • deps: update dependency hosted-git-info to v9 (9fa04f8)
  • deps: update dependency yargs to v18 (#​3745) (cde9a72)
  • deps: update to the stable version of the github plugin (f12cf81)
  • deps: update to the stable version of the release-notes-generator plugin (d9def72)
  • deps: updated to the stable version of the commit-analyzer plugin (291533b)
  • deps: upgrade to the new major version of the npm plugin, which upgrades npm to v11 for publishing (1be8290)
Features
  • node-versions: drop support for node versions v20, v21, and v23 (56d16f4)
  • node-versions: raise the minimum node version for the v24 range (116a188)
BREAKING CHANGES
  • node-versions: the minimum node version for the v24 range is now v24.10.0
  • node-versions: a minimum of node v22.14 is now required

v24.2.9

Compare Source

Bug Fixes

v24.2.8

Compare Source

Bug Fixes

v24.2.7

Compare Source

Performance Improvements

v24.2.6

Compare Source

Bug Fixes

v24.2.5

Compare Source

Bug Fixes
  • deps: raise the minimum of the defined range for marked-terminal (#​3742) (fb1ccd4)

v24.2.4

Compare Source

Bug Fixes

v24.2.3

Compare Source

Bug Fixes

v24.2.2

Compare Source

Bug Fixes

v24.2.1

Compare Source

Bug Fixes

v24.2.0

Compare Source

Features
  • clarify branch existence requirement in error messages (#​3462) (05a2ea9)

v24.1.3

Compare Source

Bug Fixes
  • branch-naming: prevent non-range versions from being identified as maintenance branches (07f2672)

v24.1.2

Compare Source

Bug Fixes

v24.1.1

Compare Source

Bug Fixes

v24.1.0

Compare Source

Features

v24.0.0

Compare Source

Bug Fixes
  • deps: upgraded to the beta of the commit-analyzer plugin (dfc3d91)
  • deps: upgraded to the beta of the release-notes-generator plugin (4a4cd92)
BREAKING CHANGES
  • deps: the commit-analyzer plugin now expects to be used with the latest major versions of
    conventional-changelog packages. if you are installing any of these packages in addition to
    semantic-release, be sure to update them as well
  • deps: the release-notes-generator plugin now expects to be used with the latest major
    versions of conventional-changelog packages. if you are installing any of these packages in addition
    to semantic-release, be sure to update them as well

v23.1.1

Compare Source

Bug Fixes

v23.1.0

Compare Source

Features

v23.0.8

Compare Source

Bug Fixes
  • deps: rename read-pkg-up -> read-package-up (4980cba)
  • deps: rename read-pkg-up -> read-package-up (#​3249) (95a8b9e)

v23.0.7

Compare Source

Bug Fixes
  • deps: update dependency find-versions to v6 (6a2b6bb)

v23.0.6

Compare Source

Bug Fixes

v23.0.5

Compare Source

Bug Fixes

v23.0.4

Compare Source

Bug Fixes

v23.0.3

Compare Source

Bug Fixes

v23.0.2

Compare Source

Bug Fixes

v23.0.1

Compare Source

Bug Fixes
  • deps: update dependency marked-terminal to v7 (9faded8)

v23.0.0

Compare Source

Bug Fixes
Features
BREAKING CHANGES

related to https://redirect.github.com/semantic-release/semantic-release/discussions/3088

v22.0.12

Compare Source

Bug Fixes
  • Revert "fix(deps): update dependency cosmiconfig to v9" (#​3104) (f6f1bf1)

v22.0.11

Compare Source

Bug Fixes
  • deps: update dependency cosmiconfig to v9 (b38cd2e)

v22.0.10

Compare Source

Bug Fixes
  • revert updating cosmiconfig to v9 (88efead)

v22.0.9

Compare Source

Bug Fixes

v22.0.8

Compare Source

Bug Fixes

v22.0.7

Compare Source

Bug Fixes
Features

v22.0.6

Compare Source

Bug Fixes

v22.0.5

Compare Source

Bug Fixes

v22.0.4

Compare Source

Bug Fixes

v22.0.3

Compare Source

Bug Fixes
  • exports: removed the exports definition for the time being (561e2d6), closes #​2968. see #​2978 for more information.

v22.0.2

Compare Source

Bug Fixes
  • deps: update dependency marked-terminal to v6 (8a7befe)

v22.0.1

Compare Source

Bug Fixes
  • deps: upgraded release-notes-generator and commit-analyzer plugins to stable versions (041e4f7), closes #​2934

v22.0.0

Compare Source

Bug Fixes
  • deps: updated to the latest beta of the commit analyzer plugin (03a687b)
  • deps: updated to the latest betas of the commit-analyzer and release-notes-generator plugins (de8e4e0)
  • deps: upgraded to the latest version of the npm plugin with npm v10 (a23b718)
Features
  • conventional-changelog-presets: supported new preset format (07a79ea)
  • defined exports for the package (72ab317)
  • node-versions: raised the minimum node v20 requirement to v20.6 (e623cc6)
  • node-versions: raised the minimum required node version to v18.17 and dropped v19 support (b9f294d)
  • node-versions: raised the minimum supported node version w/in the v20 range to v20.6.1 (b93bef4)
BREAKING CHANGES
  • node-versions: the minimum supported version for the v20 range of node has been raised slightly to
    v20.6.1 to avoid a known node bug
  • node-versions: the minimum supported node version in the v20 major range is now v20.6
  • node-versions: node v18.17 is now the minimum supported node version and support for v19 has been dropped
  • exports prevents access to internal files, but they arent intended for public use anyway
  • conventional-changelog-presets: the new preset format is a breaking change when compared to the previous preset format. updating to support the new format means that the old preset format is no longer supported. update your preset to the latest version to maintain compatibility. this is also important if you are using a preset outside of the list of official conventional-changelog presets since your preset will need to be updated to export async functions to match the expected preset signature.

v21.1.2

Compare Source

Bug Fixes

v21.1.1

Compare Source

Bug Fixes
  • types: included the definitions file in the published package (#​2920) (4c95c97)

v21.1.0

Compare Source

Features

v21.0.9

Compare Source

Bug Fixes

v21.0.8

Compare Source

Bug Fixes

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, on day 1 of the month ( * 0-3 1 * * ) in timezone Europe/Berlin, 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch 5 times, most recently from ad0e895 to 7c453fd Compare November 6, 2023 02:23
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 7c453fd to 4b437ca Compare November 17, 2023 02:15
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch 4 times, most recently from d901ee3 to 944e840 Compare December 12, 2023 00:41
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 944e840 to c9640b1 Compare December 12, 2023 06:57
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from c9640b1 to e0f0614 Compare January 13, 2024 00:23
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch 2 times, most recently from 9a4803f to 064cdec Compare February 7, 2024 15:30
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 064cdec to fd78951 Compare March 2, 2024 01:26
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch 4 times, most recently from 3ae8df5 to 21ec2ce Compare March 18, 2024 14:57
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch 2 times, most recently from 43879eb to 60bf843 Compare March 24, 2024 17:53
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch 2 times, most recently from 186fdad to f89814b Compare April 9, 2024 21:35
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch 2 times, most recently from 04ee26c to 3e1ee40 Compare May 10, 2024 19:48
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 3e1ee40 to a2d7158 Compare June 1, 2024 02:43
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from a2d7158 to 96370fb Compare June 22, 2024 07:52
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 96370fb to 3e8ba5e Compare August 17, 2024 13:46
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 4cb12fc to 51389bb Compare January 3, 2025 07:48
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch 2 times, most recently from 9ceace4 to f83aae4 Compare February 15, 2025 22:36
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from f83aae4 to 785dd6f Compare May 16, 2025 22:51
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 785dd6f to 57d5480 Compare May 23, 2025 23:39
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch 2 times, most recently from 949016b to 723b71c Compare June 29, 2025 16:33
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 723b71c to 0134f41 Compare July 11, 2025 21:45
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch 2 times, most recently from 7bcdefa to 378b7b5 Compare August 13, 2025 17:35
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 378b7b5 to a97eb23 Compare August 19, 2025 14:43
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from a97eb23 to ba161d2 Compare August 31, 2025 10:51
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch 2 times, most recently from 44db6ad to 68b8c75 Compare September 10, 2025 21:47
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch 2 times, most recently from 114dfd8 to dc99cd5 Compare September 25, 2025 14:48
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch 5 times, most recently from f60756b to d3ad27d Compare October 20, 2025 02:01
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from d3ad27d to c52f857 Compare October 21, 2025 16:51
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch 2 times, most recently from 7cf89cd to 167fa47 Compare November 11, 2025 00:06
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 167fa47 to c665a46 Compare November 15, 2025 00:38
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from c665a46 to 47f02c0 Compare December 3, 2025 19:57
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 47f02c0 to 75038bb Compare December 12, 2025 21:07
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 75038bb to 17af9fa Compare January 8, 2026 19:43
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 17af9fa to 917a0d0 Compare January 19, 2026 14:40
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.

1 participant