Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Sep 15, 2023

This PR contains the following updates:

Package Change Age Confidence
@semantic-release/exec 6.0.3 -> 7.1.0 age confidence
@semantic-release/npm 10.0.6 -> 13.1.2 age confidence
semantic-release 21.1.2 -> 25.0.2 age confidence

Release Notes

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

v7.1.0

Compare Source

Features
  • error: print more useful error for non-process failure (#​449) (a285bc5)

v7.0.3

Compare Source

Bug Fixes
  • deps: update dependency execa to v9 (643e2eb)

v7.0.2

Compare Source

Bug Fixes

v7.0.1

Compare Source

Bug Fixes

v7.0.0

Compare Source

Features
BREAKING CHANGES
  • the minimum required version of semantic-release to use @semantic-release/exec is now v24.1.0; the warn logger method/function is now available to use in plugin

  • @semantic-release/exec is now a native ES Module. It has named exports for each plugin hook (verifyConditions, analyzeCommits, verifyRelease, generateNotes, prepare, publish, addChannel, success, fail)

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
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.

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

@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 24df939 to 70e6563 Compare September 16, 2023 10:02
@renovate renovate bot changed the title chore(deps): update dependency @semantic-release/npm to v11 chore(deps): update semantic-release monorepo (major) Sep 16, 2023
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 6 times, most recently from 0b3569e to 5eb8d96 Compare September 23, 2023 00:09
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 5 times, most recently from 024e770 to e989cca Compare September 29, 2023 17:35
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from dbff6bb to b84b80d Compare October 7, 2023 02:26
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 2e7eb4b to 6b12612 Compare October 18, 2023 15:18
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 4 times, most recently from 0b61be4 to c0202cc Compare October 31, 2023 10:33
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 573b3f4 to 4f62a1f Compare November 8, 2023 00:32
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 4f62a1f to ed333f9 Compare November 17, 2023 04:35
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 4 times, most recently from 22c833c to 63bccc1 Compare December 12, 2023 00:48
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from f8ef148 to e580842 Compare January 23, 2025 13:06
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 38d6bbc to 2d4d332 Compare February 3, 2025 05:33
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from a548ade to 40312c5 Compare February 15, 2025 22:43
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 40312c5 to 2e3b54b Compare May 9, 2025 22:04
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 87872e7 to c700d78 Compare May 20, 2025 13:29
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from c700d78 to f68d0f3 Compare May 24, 2025 01:59
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 95242a5 to 78e21ec Compare June 29, 2025 18:41
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 78e21ec to df20f7c Compare July 11, 2025 22:52
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from fca1c97 to 6e4a251 Compare August 11, 2025 16:58
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 6e4a251 to 6a94eec Compare August 19, 2025 18:38
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 4ec6fba to 3606c77 Compare September 4, 2025 08:33
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 3606c77 to b5e125a Compare September 10, 2025 22:08
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 3eca6b3 to 2348161 Compare September 25, 2025 14:08
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 5 times, most recently from e47d393 to 1a9d200 Compare October 19, 2025 21:31
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 1a9d200 to ff68bf7 Compare October 21, 2025 17:02
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 3fc8885 to e2712ea Compare November 10, 2025 21:11
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from e2712ea to 193182c Compare November 15, 2025 00:04
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