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

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@semantic-release/commit-analyzer	9.0.2 -> 13.0.0
semantic-release	21.0.7 -> 24.1.2

---

Release Notes

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

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

v11.1.0

Compare Source

Features

• add support for ESM presets (#​537) (9dc87e0)

v11.0.0

Compare Source

Bug Fixes

• config-loader: accounted for normalization of preset interfaces (3ff9458)
• deps: update dependency conventional-commits-filter to v4 (99dcf7e)

Features

• conventional-changelog-presets: supported new preset format (f3b88d3)
• node-versions: raised the minimum node version to v18.17 and dropped v19 support (a681fbd)

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

v10.0.4

Compare Source

Bug Fixes

• deps: update dependency conventional-commits-parser to v5 (a7201b6)

v10.0.3

Compare Source

Reverts

• Revert "fix(deps): update dependency conventional-commits-parser to v5 (#​501)" (ab3ee9f), closes #​501
• Revert "chore(deps): update dependency conventional-changelog-atom to v4 (#​502)" (f21eb8e), closes #​502
• Revert "chore(deps): update dependency conventional-changelog-ember to v4 (#​504)" (c48b533), closes #​504

v10.0.2

Compare Source

Bug Fixes

• deps: update dependency conventional-commits-parser to v5 (#​501) (91cf4d5)

v10.0.1

Compare Source

Bug Fixes

• deps: update dependency conventional-changelog-angular to v6 (#​460) (0607201)
• deps: update dependency conventional-commits-filter to v3 (#​461) (97d683f)
• deps: update dependency conventional-commits-parser to v4 (#​462) (5d94efa)

v10.0.0

Compare Source

Code Refactoring

• esm: converted the package to esm (b4f9865), closes #​296

Features

• deps: raised the peer-dependency requirement on semantic-release to v20.1.0 (e1ab8ea)
• node-versions: raised the minimum required node version to v18 (affeb23)

BREAKING CHANGES

• deps: the minimum required version of semantic-release is now v20.1.0 in order to support
  loading ESM plugins
• node-versions: the minimum required version of node is now v18
• esm: @semantic-release/commit-analyzer is now a native ES Module. It has named exports
  for each plugin hook (analyzeCommits)

semantic-release/semantic-release (semantic-release)

v24.1.2

Compare Source

Bug Fixes

• deps: update @semantic-release/github to v11.0.0 (#​3460) (43df51b)

v24.1.1

Compare Source

v24.1.0

Compare Source

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

v23.1.0

Compare Source

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

v23.0.6

Compare Source

Bug Fixes

• deps: update dependency @​semantic-release/release-notes-generator to v13 (#​3237) (b7e08fc)

v23.0.5

Compare Source

v23.0.4

Compare Source

v23.0.3

Compare Source

v23.0.2

Compare Source

Bug Fixes

• deps: update dependency marked to v12 (#​3176) (38105f5)

v23.0.1

Compare Source

Bug Fixes

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

v23.0.0

Compare Source

Bug Fixes

• deps: update dependency cosmiconfig to v9 (#​3105) (07dde04)
• deps: update dependency marked to v11 (#​3079) (6d2a6f1)
• deps: upgraded to the latest version of env-ci (0d0ed9d)
• use one note reference per tag to prevent conflicts (#​2085) (020ea7d)

Features

• node-versions: dropped support for node v18 and raised the minimum for v20 (2904832), closes /github.com/semantic-release/gitlab/pull/647#discussion_r1423131205

BREAKING CHANGES

• deps: woodpecker ci users need to upgrade to v1.0.0 or higher to remain supported. see
  https://github.com/semantic-release/env-ci/releases/tag/v11.0.0 for more information
• node-versions: support for node v18 has been dropped and the minimum for v20 is now v20.8.1

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

• deps: if using release.config.js as the name of your config file, it needs to be moved to a .config/ directory. see https://github.com/cosmiconfig/cosmiconfig/releases/tag/v9.0.0 for more detail

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

• deps: update dependency cosmiconfig to v9 (#​3072) (8b0dbd2)

v22.0.8

Compare Source

Bug Fixes

• support windows absolute extends (#​3062) (0d06f62)

v22.0.7

Compare Source

Bug Fixes

• deps: update dependency read-pkg-up to v11 (#​3047) (f09e55f)

Features

• support extending ESM configuration files (#​3036)(6900865)

v22.0.6

Compare Source

Bug Fixes

• deps: update dependency figures to v6 (#​3033) (305674d)

v22.0.5

Compare Source

Bug Fixes

• deps: update dependency env-ci to v10 (#​2983) (e759493)

v22.0.4

Compare Source

Bug Fixes

• deps: update dependency marked to v9 (#​2947) (84f2ee9)

v22.0.3

Compare Source

Bug Fixes

• exports: removed the exports definition for the time being (561e2d6), closes #​2968. see https://github.com/semantic-release/semantic-release/issues/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

• deps: update dependency aggregate-error to v5 (#​2956) (1017e1a)

v21.1.1

Compare Source

Bug Fixes

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

v21.1.0

Compare Source

Features

• Added TypeScript definitions (#​2916) (c21a1ac)

v21.0.9

Compare Source

Bug Fixes

• deps: update dependency hosted-git-info to v7 (#​2908) (eba86ac)

v21.0.8

Compare Source

Bug Fixes

• deps: update dependency execa to v8 (#​2914) (7bc21fc)

---

Configuration

📅 Schedule: Branch creation - "after 3am and before 10pm" (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]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @outreach/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/semantic-release
npm ERR!   dev semantic-release@"23.0.8" from the root project
npm ERR!   peer semantic-release@">=18.0.0" from @semantic-release/[email protected]
npm ERR!   node_modules/@semantic-release/changelog
npm ERR!     dev @semantic-release/changelog@"6.0.3" from the root project
npm ERR!   5 more (@semantic-release/git, @semantic-release/github, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer semantic-release@">=19.0.0 <20.0.0" from @outreach/[email protected]
npm ERR! node_modules/@outreach/semantic-release-circleci-orb
npm ERR!   dev @outreach/semantic-release-circleci-orb@"^1.1.9" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/semantic-release
npm ERR!   peer semantic-release@">=19.0.0 <20.0.0" from @outreach/[email protected]
npm ERR!   node_modules/@outreach/semantic-release-circleci-orb
npm ERR!     dev @outreach/semantic-release-circleci-orb@"^1.1.9" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-04-09T23_19_51_059Z-debug-0.log

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @outreach/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/semantic-release
npm ERR!   dev semantic-release@"24.1.2" from the root project
npm ERR!   peer semantic-release@">=18.0.0" from @semantic-release/[email protected]
npm ERR!   node_modules/@semantic-release/changelog
npm ERR!     dev @semantic-release/changelog@"6.0.3" from the root project
npm ERR!   5 more (@semantic-release/git, @semantic-release/github, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer semantic-release@">=19.0.0 <20.0.0" from @outreach/[email protected]
npm ERR! node_modules/@outreach/semantic-release-circleci-orb
npm ERR!   dev @outreach/semantic-release-circleci-orb@"^1.1.9" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/semantic-release
npm ERR!   peer semantic-release@">=19.0.0 <20.0.0" from @outreach/[email protected]
npm ERR!   node_modules/@outreach/semantic-release-circleci-orb
npm ERR!     dev @outreach/semantic-release-circleci-orb@"^1.1.9" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-09-27T17_08_44_273Z-debug-0.log

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.