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 #172

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

Mend Renovate

This PR contains the following updates:

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

Release Notes

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

v24.0.0

Compare Source

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 has been generated by Mend Renovate. View repository job log here.

@socket-security
Copy link

socket-security bot commented Sep 17, 2023

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

Package New capabilities Transitives Size Publisher
npm/semantic-release@24.0.0 environment, network Transitive: eval, filesystem, shell, unsafe +259 34.8 MB semantic-release-bot

🚮 Removed packages: npm/semantic-release@21.1.2

View full report↗︎

@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch 4 times, most recently from 310e35c to dfff26c Compare September 25, 2023 16:42
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch from dfff26c to e369659 Compare October 13, 2023 03:32
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch from e369659 to 175a1f9 Compare October 22, 2023 10:48
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch 2 times, most recently from aa91717 to 87aa372 Compare November 4, 2023 21:48
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch from 87aa372 to 48d4202 Compare November 18, 2023 03:06
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch 3 times, most recently from 245fdaf to 4586842 Compare December 13, 2023 00:27
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch from 4586842 to c5371a4 Compare December 13, 2023 06:07
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch from c5371a4 to 860a1c7 Compare January 14, 2024 00:37
@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 5 times, most recently from 5cf1622 to f9ce485 Compare January 16, 2024 13:13
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch from f9ce485 to ef62cac Compare January 26, 2024 12:17
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch 2 times, most recently from 2a0e33a to ac89c98 Compare February 8, 2024 16:02
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch from ac89c98 to 50ac1e0 Compare February 16, 2024 00:09
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch 3 times, most recently from 59a54d6 to fb18b55 Compare March 19, 2024 17:59
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch from fb18b55 to 1c3ca68 Compare March 25, 2024 18:11
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch 2 times, most recently from 9b40cd5 to 2ca50ca Compare April 10, 2024 23:08
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch 2 times, most recently from be1e476 to ff1a30c Compare May 11, 2024 22:08
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch from ff1a30c to 2fcabf5 Compare June 2, 2024 02:09
@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 from 2fcabf5 to 421bfc4 Compare June 16, 2024 06:48
@renovate renovate bot force-pushed the renovate_major-semantic-release-monorepo branch from 421bfc4 to 3c1980f Compare June 17, 2024 21:48
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.

None yet

0 participants