Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jan 13, 2024

This PR contains the following updates:

Package Change Age Confidence
@semantic-release/exec 6.0.3 -> 7.1.0 age confidence
semantic-release ^22.0.12 -> ^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/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


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 added the renovate label Jan 13, 2024
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from d8c33b8 to 75370c2 Compare February 8, 2024 09:36
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 999ea8f to edd4190 Compare March 5, 2024 19:51
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 4 times, most recently from dd4101f to 67c9945 Compare March 18, 2024 14:22
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 72d6e49 to 8fe74bf Compare March 28, 2024 07:26
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from b90f64f to f759860 Compare April 9, 2024 22:13
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from f759860 to b9ac802 Compare April 11, 2024 13:22
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from b9ac802 to 7dfa5f2 Compare May 10, 2024 20:01
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 6d54ae6 to ebb1b06 Compare May 26, 2024 18:17
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v23 chore(deps): update dependency semantic-release to v24 May 31, 2024
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from be162f4 to a3eca12 Compare June 3, 2024 03:38
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from a3eca12 to a437077 Compare June 21, 2024 19:43
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from a437077 to b632101 Compare August 5, 2024 03:23
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 4c77319 to a2d9bd7 Compare August 19, 2024 14:09
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 316754f to a0f3a76 Compare September 11, 2024 04:55
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from a0f3a76 to 1b685b8 Compare September 14, 2024 03:27
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 1b685b8 to 6c8dd97 Compare September 27, 2024 18:08
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 6c8dd97 to ce59652 Compare October 19, 2024 01:29
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 936e13e to d056c8b Compare February 3, 2025 05:01
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from fdf2fd7 to d401801 Compare February 15, 2025 21:55
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 108d7ee to 46126f6 Compare April 10, 2025 22:59
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 46126f6 to dc33e5c Compare April 23, 2025 07:35
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 73cba4f to 55c64da Compare May 16, 2025 22:12
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 6e8aae6 to 50fd50a Compare May 23, 2025 23:05
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 50fd50a to 840f1bd Compare May 30, 2025 10:10
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from fe23666 to 6c8a497 Compare July 5, 2025 01:16
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 6c8a497 to a5fad07 Compare July 11, 2025 22:03
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 0022ee9 to 9d7e549 Compare August 13, 2025 11:42
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 9d7e549 to 094902f Compare August 19, 2025 19:09
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 094902f to 8aff03c Compare August 31, 2025 12:26
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 8aff03c to 342f1c9 Compare September 10, 2025 22:36
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 44fb70d to befd724 Compare September 25, 2025 20:49
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from dbc2c24 to 0c15156 Compare October 21, 2025 22:14
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from d90a34f to 3e01756 Compare November 10, 2025 20:15
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 3e01756 to c8e7318 Compare November 18, 2025 11:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant