Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Mar 18, 2024

This PR contains the following updates:

Package Change Age Confidence
@semantic-release/commit-analyzer 11.1.0 -> 13.0.1 age confidence
@semantic-release/github 9.2.6 -> 12.0.1 age confidence
@semantic-release/npm 11.0.3 -> 13.1.1 age confidence
@semantic-release/release-notes-generator 12.1.0 -> 14.1.0 age confidence
semantic-release 23.0.2 -> 25.0.2 age confidence

Release Notes

semantic-release/commit-analyzer (@​semantic-release/commit-analyzer)

v13.0.1

Compare Source

Bug Fixes

v13.0.0

Compare Source

Bug Fixes
  • log the raw message again (e2f5d6c)
Features
  • support latest conventional-changelog packages (0254d7a)
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

v12.0.0

Compare Source

Features
  • exports: defined exports to point at ./index.js (f3358dd)
  • node-versions: dropped support for node v18 and v19 (0a23b82)
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
semantic-release/github (@​semantic-release/github)

v12.0.1

Compare Source

Bug Fixes

v12.0.0

Compare Source

Features
  • node-versions: drop support for node versions v20, v21, and v23 (6e2ac27)
  • node-versions: raise the minimum node version requirement for the v24 range (4d6924d)
  • remove github search api consumption (#​1037) (d260bfd), closes #​1022
BREAKING CHANGES
  • node-versions: the minimum node version for the v24 range is now v24.10.0
  • @semantic-release/github no longer consumes the GitHub Search API in the plugin
  • node-versions: a minimum of node v22.14 is now required

v11.0.6

Compare Source

Bug Fixes

v11.0.5

Compare Source

Bug Fixes

v11.0.4

Compare Source

Bug Fixes

v11.0.3

Compare Source

Bug Fixes

v11.0.2

Compare Source

Bug Fixes

v11.0.1

Compare Source

Bug Fixes

v11.0.0

Compare Source

chore
  • update peer dependency for semantic-release (95c7cdd)
Code Refactoring
  • modify commit associatedPRs and relatedIssues label property data type. (718134a)
Features
  • integrate warn in fail script (7a9914a)
  • integrate warn in success script (792720d)
BREAKING CHANGES
  • the commit associatedPR and relatedIssues label prop is now an array of objects with more properties
  • the minimum required version of semantic-release to use
    @​semantic-release/github is now v24.1.0

v10.3.5

Compare Source

Bug Fixes
  • replace searchAPI usage with GraphQL in findSRIssue util (#​907) (7fb46a3)

v10.3.4

Compare Source

Bug Fixes
  • glob-assets: remove unnecessary option when invoking globby() (#​924) (efe9f49)

v10.3.3

Compare Source

Bug Fixes
  • Revert: feat: verify OAuth scopes of classic GitHub PATs (#​915) (990bd73)

v10.3.2

Compare Source

Bug Fixes
  • missing "PullRequest".canBeRebased field on GHES graphql api (#​913) (4393578)

v10.3.1

Compare Source

Bug Fixes
  • max_node_limit_exceeded error when fetching associatedPRs (#​912) (bb806af)

v10.3.0

Compare Source

Features
  • allow conditional skip on success and fail comments (#​874) (e097d1c)

v10.2.0

Compare Source

Features

v10.1.7

Compare Source

Bug Fixes

v10.1.6

Compare Source

Bug Fixes
  • edge-case: fetching associatedPRs on 100+ context.commits in success lifecycle (#​892) (dfe47e9)

v10.1.5

Compare Source

Bug Fixes

v10.1.4

Compare Source

Bug Fixes
  • docs: correct docs branch for fail-comment links (#​893) (b591730)

v10.1.3

Compare Source

Bug Fixes

v10.1.2

Compare Source

Bug Fixes

v10.1.1

Compare Source

Bug Fixes
  • invalid GraphQL query generated when no release commits are found (#​876) (8ee2744)

v10.1.0

Compare Source

Features

v10.0.7

Compare Source

Bug Fixes
  • replace github search api with graphql in success lifecycle method (#​857) (be394cf)

v10.0.6

Compare Source

Bug Fixes
  • corrected homepage link in package.json so the generated links in the errors are valid (#​848) (865762d)

v10.0.5

Compare Source

Bug Fixes

v10.0.4

Compare Source

Bug Fixes
  • introduce dedicated option for GitHub API endpoint (#​829) (908ff83)

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

Features
  • node-versions: dropped support for node v18 and v19 (#​797) (aea314f)
BREAKING CHANGES
  • node-versions: node v18 and v19 are no longer supported
semantic-release/npm (@​semantic-release/npm)

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
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
semantic-release/semantic-release (semantic-release)

v25.0.2

Compare Source

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

Configuration

📅 Schedule: Branch creation - "before 4am on monday" (UTC), 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 changed the title dev dependency update: @semantic-release/github (major) dev dependency update: @semantic-release/commit-analyzer (major) Mar 18, 2024
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 4a22765 to 0c3c3fc Compare March 24, 2024 07:32
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 0c3c3fc to 60f0fa5 Compare April 6, 2024 20:32
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from f61a5f3 to fa51bdd Compare May 16, 2024 00:20
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from fa51bdd to 583c08f Compare May 22, 2024 19:38
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 11bcbab to f3712b8 Compare June 5, 2024 05:00
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from f3712b8 to a6974d5 Compare June 22, 2024 04:48
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 0b6642e to 5760259 Compare July 8, 2024 14:11
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from d54dbec to 4916c3d Compare July 17, 2024 17:09
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 84c5bf4 to 8df0eaa Compare July 26, 2024 01:04
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 339aaa5 to 152d1ee Compare August 15, 2024 20:24
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 07f5163 to f7a0ac1 Compare August 20, 2024 20:01
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 4 times, most recently from 54578d7 to 12c8311 Compare September 6, 2024 00:04
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from d821ce7 to 77439c6 Compare September 15, 2024 15:51
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from cf8729e to a2027f3 Compare May 23, 2025 12:28
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 545f898 to 65d4312 Compare May 25, 2025 13:23
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 65d4312 to 1ffdd4d Compare June 2, 2025 04:41
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 1ffdd4d to cbd22b3 Compare June 17, 2025 20:40
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 4 times, most recently from 0ce9bab to babd35a Compare June 30, 2025 06:27
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from babd35a to cfa63ef Compare July 11, 2025 20:24
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from cfa63ef to d6f7393 Compare July 19, 2025 02:31
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 91e1491 to 7968323 Compare August 11, 2025 00:52
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 7968323 to 2f319c8 Compare August 19, 2025 17:06
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 450ec72 to 3b0cbb2 Compare September 6, 2025 23:50
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 4cb22e3 to 47e5a1c Compare September 11, 2025 06:11
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 8c8d4ac to 0a6d05f Compare September 25, 2025 16:06
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 5 times, most recently from 72ac708 to 9325c2c Compare October 20, 2025 01:01
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 9325c2c to d69b569 Compare October 21, 2025 09:47
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from d69b569 to a8f8d22 Compare October 31, 2025 23:43
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from a8f8d22 to 4c7ebe7 Compare November 7, 2025 22:44
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