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) #506

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 28, 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 19.0.5 -> 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.

v21.1.2

Compare Source

Bug Fixes

v21.1.1

Compare Source

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

v21.1.0

Compare Source

Features

v21.0.9

Compare Source

Bug Fixes

v21.0.8

Compare Source

Bug Fixes

v21.0.7

Compare Source

Bug Fixes

v21.0.6

Compare Source

Bug Fixes
  • get correct version if prerelease branch shares version with ... (#​2416) (e4229f9)

v21.0.5

Compare Source

Bug Fixes
  • deps: update dependency marked to v5 (452e1fa)

v21.0.4

Compare Source

Bug Fixes

v21.0.3

Compare Source

Bug Fixes
  • bump @semantic-release/commit-analyzer to v10.0.0-beta.1 (4a6b31f)
  • bump @semantic-release/github to 9.0.0-beta.2 (#​2818) (6f19d77)
  • deps: updated the beta plugins to stable versions (3941018)

v21.0.2

Compare Source

Bug Fixes

v21.0.1

Compare Source

Bug Fixes

v21.0.0

Compare Source

BREAKING CHANGES
  • deps: the npm plugin has updated the npm dependency to v9
  • legacy authentication using NPM_USERNAME and NPM_PASSWORD is no longer supported. Use NPM_TOKEN instead.
Bug Fixes
  • deps: bump @semantic-release/npm to ^10.0.0 (d647433)

v20.1.3

Compare Source

Bug Fixes
  • deps: update dependency execa to v7.1.1 (c38b53a)

v20.1.2

Compare Source

Bug Fixes
  • deps: update dependency cosmiconfig to v8.1.2 (fbede54)

v20.1.1

Compare Source

Bug Fixes

v20.1.0

Compare Source

Features

v20.0.4

Compare Source

Bug Fixes
  • windows: fixed issues preventing execution from windows (#​2672) (5df624c)

v20.0.3

Compare Source

Reverts

v20.0.2

Compare Source

Bug Fixes

v20.0.1

Compare Source

Bug Fixes
  • deps: update dependency cosmiconfig to v8 (f914c1e)
  • deps: update dependency hosted-git-info to v6 (c4da008)

v20.0.0

Compare Source

BREAKING CHANGES
  • esm: semantic-release is now ESM-only. since it is used through its own executable, the impact on consuming projects should be minimal
  • esm: references to plugin files in configs need to include the file extension because of executing in an ESM context
  • node-versions: node v18 is now the minimum required version of node. this is in line with our node support policy. please see our recommendations for releasing with a different node version than your project normally uses, if necessary.
Features
Bug Fixes
  • env-ci: updated to the stable esm-only version (#​2632) (918eb59)
  • secrets-masking: used the proper named import from hook-std to enable masking for stderr (#​2619) (cf6befa)

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 May 28, 2023
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from a53d3be to 7d1d1cf Compare June 2, 2023 22:52
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v21 fix(deps): update semantic-release monorepo (major) Jun 7, 2023
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 85a3119 to b9ffbae Compare June 14, 2023 12:21
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 3fc189c to 66c424d Compare July 5, 2023 01:35
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 66c424d to 69dc870 Compare August 20, 2023 01:30
@renovate
Copy link
Contributor Author

renovate bot commented Aug 20, 2023

⚠ 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

@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 6afd7f5 to 847dca3 Compare August 24, 2023 20:20
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 1c7e576 to f30f5ea Compare September 16, 2023 23:16
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from f30f5ea to 1c6243b Compare October 1, 2023 14:26
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from c05bcf4 to f5b2d06 Compare November 3, 2023 22:27
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from f5b2d06 to ec96d00 Compare November 17, 2023 03:53
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from d68bf84 to ff8ffba Compare December 12, 2023 01:46
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from ff8ffba to bbfb3ae Compare December 12, 2023 07:13
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from bbfb3ae to 2f8f55a Compare January 12, 2024 22:52
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 1a17f14 to c3c422e Compare February 7, 2024 16:12
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from a317a7f to 5c3623d Compare March 18, 2024 17:17
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 5c3623d to cfe8f29 Compare March 24, 2024 17:55
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from cfe8f29 to 0aed422 Compare April 3, 2024 18:56
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 0aed422 to 6c801d3 Compare April 9, 2024 22:56
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 6c801d3 to c85166a Compare May 10, 2024 18:12
Copy link
Contributor Author

renovate bot commented May 10, 2024

⚠️ 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

@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from c85166a to 8047d7a Compare May 10, 2024 21:20
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 8047d7a to 963317e Compare June 1, 2024 02:25
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 963317e to 0732756 Compare August 17, 2024 12:59
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 0732756 to 598d6c8 Compare September 11, 2024 06:51
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 598d6c8 to f69bcdd Compare September 27, 2024 18:12
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from f69bcdd to 3bf970a Compare October 18, 2024 23:29
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 3bf970a to 75369b7 Compare October 25, 2024 19:31
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.

0 participants