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

fix(deps): update semantic-release monorepo (major) #353

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 7, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@semantic-release/error ^3.0.0 -> ^4.0.0 age adoption passing confidence
semantic-release 21.1.2 -> 24.2.0 age adoption passing confidence

Release Notes

semantic-release/error (@​semantic-release/error)

v4.0.0

Compare Source

Code Refactoring
BREAKING CHANGES
  • esm: @semantic-release/error is now an ES Module
  • esm: the minimum required version of node is now v18
semantic-release/semantic-release (semantic-release)

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 is behind base branch, 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 force-pushed the renovate/major-semantic-release-monorepo branch 4 times, most recently from 8a7a21b to c35c86d Compare June 12, 2023 19:51
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from ddada8b to a302d39 Compare June 26, 2023 03:55
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from ae0af20 to 3fa61de Compare July 5, 2023 07:59
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from e8b333f to bacef4a Compare July 10, 2023 04:38
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from bacef4a to 6ee6c2a Compare July 17, 2023 03:10
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 4 times, most recently from ddc5f7b to d3cee77 Compare August 20, 2023 07:16
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 642e7ee to b6e64df Compare August 24, 2023 23:06
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from b6e64df to ba894b1 Compare September 4, 2023 16:16
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 1854dfe to 2302d1b Compare September 16, 2023 11:13
@renovate renovate bot changed the title fix(deps): update dependency @semantic-release/error to v4 fix(deps): update semantic-release monorepo (major) Sep 16, 2023
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 4 times, most recently from 5b67f39 to fbd52b3 Compare September 23, 2023 01:08
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from fbd52b3 to 2843bd7 Compare September 24, 2023 18:05
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 2843bd7 to 3a73731 Compare October 5, 2023 16:35
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 8bf3715 to da66958 Compare December 18, 2023 16:46
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from da66958 to 68cf313 Compare January 1, 2024 21:43
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 68cf313 to ae29b71 Compare January 12, 2024 22:13
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 31da9dc to aed4bfb Compare February 7, 2024 15:52
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from f342902 to 3c56614 Compare March 18, 2024 17:54
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 3c56614 to 85825d4 Compare March 24, 2024 16:00
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 9307688 to 7cfd313 Compare April 9, 2024 22:34
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 7cfd313 to 7aeb748 Compare April 22, 2024 19:06
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 0544f03 to 0bf59ff Compare May 10, 2024 22:03
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 0bf59ff to 6e640c7 Compare May 31, 2024 22:55
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 6e640c7 to bb9be2d Compare August 17, 2024 16:15
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from bb9be2d to edf7ff3 Compare September 11, 2024 04:26
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from edf7ff3 to 26425d3 Compare September 27, 2024 18:58
@babblebey babblebey mentioned this pull request Oct 9, 2024
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 26425d3 to 268cbc4 Compare October 18, 2024 22:06
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 268cbc4 to f84ed0f Compare October 25, 2024 20:14
Copy link
Contributor Author

renovate bot commented Dec 12, 2024

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.

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