Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency semantic-release to v24 #37

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 17, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
semantic-release 21.1.2 -> 24.2.1 age adoption passing confidence

Release Notes

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

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

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

v23.0.5

Compare Source

v23.0.4

Compare Source

v23.0.3

Compare Source

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://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

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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • 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 5 times, most recently from e34c11c to e5ef650 Compare September 25, 2023 18:39
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch from e5ef650 to 4d88d8c Compare October 13, 2023 01:26
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch from 4d88d8c to b82e49e Compare October 22, 2023 10:54
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch 2 times, most recently from 9deaa4e to cd7c17a Compare November 4, 2023 21:53
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch from cd7c17a to c0b4d38 Compare November 18, 2023 05:01
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch 3 times, most recently from 40da393 to 991f0a1 Compare December 13, 2023 00:03
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch from 991f0a1 to 2d7f295 Compare December 13, 2023 07:47
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch from 2d7f295 to 7cad07d Compare January 14, 2024 01:04
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v22 chore(deps): update dependency semantic-release to v23 Jan 14, 2024
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch from 7cad07d to c4a514a Compare January 14, 2024 12:27
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch from c4a514a to ed400ea Compare January 26, 2024 11:51
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch 2 times, most recently from af3c849 to bf1ad89 Compare February 8, 2024 15:15
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch from bf1ad89 to f3800e7 Compare February 16, 2024 03:03
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch 3 times, most recently from 428d69a to c582ee5 Compare March 19, 2024 14:32
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch from c582ee5 to e6c48aa Compare March 25, 2024 16:12
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch 2 times, most recently from ebb6d85 to ab70d19 Compare April 10, 2024 22:03
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch 2 times, most recently from 59b7103 to fb51ed2 Compare May 11, 2024 22:51
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch from fb51ed2 to 4ec8232 Compare June 2, 2024 00:18
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v23 chore(deps): update dependency semantic-release to v24 Jun 2, 2024
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch 2 times, most recently from e785a9b to b32abc5 Compare June 17, 2024 22:50
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch from b32abc5 to 53f60be Compare August 18, 2024 13:03
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch from 53f60be to 9b59e4a Compare September 12, 2024 05:01
Copy link

socket-security bot commented Sep 12, 2024

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

View full report↗︎

@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch from 9b59e4a to 6c82fb6 Compare September 17, 2024 04:10
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch from 6c82fb6 to 0bb1481 Compare September 28, 2024 19:40
Copy link

socket-security bot commented Sep 28, 2024

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/[email protected] Transitive: environment, eval, filesystem, network, shell, unsafe +220 34.3 MB gr2m, pvdlg, semantic-release-bot, ...1 more

🚮 Removed packages: npm/[email protected], npm/[email protected]

View full report↗︎

@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch 2 times, most recently from cebda6e to e9a5860 Compare October 26, 2024 19:56
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch from e9a5860 to 7bddfca Compare January 7, 2025 14:55
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.

0 participants