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(npm): update dependency semantic-release to v24 #666

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 11, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
semantic-release 19.0.5 -> 24.2.0 age adoption passing confidence

Release Notes

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 - "after 8:00 pm" in timezone Asia/Tokyo, 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 added the dependencies Pull requests that update a dependency file label Jan 11, 2023
@renovate renovate bot requested a review from 3846masa January 11, 2023 14:05
@renovate renovate bot force-pushed the renovate/major-semantic-release branch from a6a73be to c2a5bdf Compare January 15, 2023 20:00
@renovate renovate bot force-pushed the renovate/major-semantic-release branch 3 times, most recently from 76747c5 to dd27e9b Compare January 28, 2023 06:39
@renovate renovate bot force-pushed the renovate/major-semantic-release branch from dd27e9b to e5eb44b Compare March 3, 2023 06:01
@renovate renovate bot force-pushed the renovate/major-semantic-release branch 2 times, most recently from c04fe4b to 858f112 Compare March 20, 2023 21:50
@renovate renovate bot force-pushed the renovate/major-semantic-release branch from 858f112 to 9463081 Compare March 27, 2023 23:42
@renovate renovate bot changed the title chore(npm): update dependency semantic-release to v20 chore(npm): update dependency semantic-release to v21 Mar 27, 2023
@renovate renovate bot force-pushed the renovate/major-semantic-release branch from 9463081 to 17fec97 Compare March 28, 2023 13:03
@renovate renovate bot force-pushed the renovate/major-semantic-release branch from 17fec97 to 7692771 Compare April 4, 2023 15:11
@renovate renovate bot force-pushed the renovate/major-semantic-release branch 2 times, most recently from 1dd92ee to bbfef8f Compare May 1, 2023 23:10
@renovate renovate bot force-pushed the renovate/major-semantic-release branch from bbfef8f to c157768 Compare May 28, 2023 14:58
@renovate renovate bot force-pushed the renovate/major-semantic-release branch 2 times, most recently from 0e7493e to 829224a Compare June 9, 2023 16:29
@renovate renovate bot force-pushed the renovate/major-semantic-release branch from 829224a to 5dc693e Compare June 14, 2023 12:35
@renovate renovate bot force-pushed the renovate/major-semantic-release branch from 5dc693e to 6fb63ce Compare June 22, 2023 15:36
@renovate renovate bot force-pushed the renovate/major-semantic-release branch 4 times, most recently from 1a32155 to 33b6cf5 Compare July 8, 2023 01:55
@renovate renovate bot force-pushed the renovate/major-semantic-release branch 2 times, most recently from 242dfdc to 5b4dda0 Compare July 16, 2023 15:33
@renovate renovate bot force-pushed the renovate/major-semantic-release branch 2 times, most recently from 778acd4 to 700ec68 Compare August 1, 2023 02:24
@renovate renovate bot force-pushed the renovate/major-semantic-release branch 2 times, most recently from dfb1b37 to 858e394 Compare August 23, 2023 04:19
@renovate renovate bot force-pushed the renovate/major-semantic-release branch 2 times, most recently from 8bb22b8 to cefbc35 Compare January 16, 2024 00:09
@renovate renovate bot changed the title chore(npm): update dependency semantic-release to v22 chore(npm): update dependency semantic-release to v23 Jan 16, 2024
@renovate renovate bot force-pushed the renovate/major-semantic-release branch from cefbc35 to 305f0a6 Compare January 16, 2024 20:41
Copy link
Contributor Author

renovate bot commented Jan 16, 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: pnpm-lock.yaml
Progress: resolved 1, reused 0, downloaded 0, added 0
undefined
 ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)

This error happened while installing a direct dependency of /tmp/renovate/repos/github/3846masa/axios-cookiejar-support

Your Node version is incompatible with "[email protected]".

Expected version: >=20.8.1
Got: v18.20.2

This is happening because the package's manifest has an engines.node field specified.
To fix this issue, install the required Node version.

@renovate renovate bot force-pushed the renovate/major-semantic-release branch 2 times, most recently from 4abd942 to 5d6053f Compare February 10, 2024 16:59
@renovate renovate bot force-pushed the renovate/major-semantic-release branch 3 times, most recently from 7056a1b to 24a9938 Compare March 21, 2024 14:57
@renovate renovate bot force-pushed the renovate/major-semantic-release branch from 24a9938 to ff9c9dc Compare March 27, 2024 18:13
@renovate renovate bot force-pushed the renovate/major-semantic-release branch 2 times, most recently from fd4ecf4 to b7d843e Compare April 12, 2024 23:18
@renovate renovate bot force-pushed the renovate/major-semantic-release branch from b7d843e to 6375011 Compare May 3, 2024 18:43
@renovate renovate bot force-pushed the renovate/major-semantic-release branch from 6375011 to 3aca374 Compare May 13, 2024 19:58
Copy link
Contributor Author

renovate bot commented May 13, 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: pnpm-lock.yaml
Progress: resolved 1, reused 0, downloaded 0, added 0
undefined
 ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)

This error happened while installing a direct dependency of /tmp/renovate/repos/github/3846masa/axios-cookiejar-support

Your Node version is incompatible with "[email protected]".

Expected version: >=20.8.1
Got: v18.20.4

This is happening because the package's manifest has an engines.node field specified.
To fix this issue, install the required Node version.

@renovate renovate bot force-pushed the renovate/major-semantic-release branch 2 times, most recently from 0c39160 to b927d00 Compare May 17, 2024 20:48
@renovate renovate bot force-pushed the renovate/major-semantic-release branch from b927d00 to e5e1a88 Compare June 4, 2024 00:43
@renovate renovate bot changed the title chore(npm): update dependency semantic-release to v23 chore(npm): update dependency semantic-release to v24 Jun 4, 2024
@renovate renovate bot force-pushed the renovate/major-semantic-release branch 2 times, most recently from 2b22d8b to fbec404 Compare July 12, 2024 12:18
@renovate renovate bot force-pushed the renovate/major-semantic-release branch from fbec404 to 327d5ff Compare August 4, 2024 16:30
@renovate renovate bot force-pushed the renovate/major-semantic-release branch from 327d5ff to 1461f40 Compare August 20, 2024 14:00
@renovate renovate bot force-pushed the renovate/major-semantic-release branch from 1461f40 to 888d56d Compare September 14, 2024 04:15
@renovate renovate bot force-pushed the renovate/major-semantic-release branch 2 times, most recently from 3fb0241 to a8a5ada Compare September 30, 2024 18:24
@renovate renovate bot force-pushed the renovate/major-semantic-release branch from a8a5ada to 28b2323 Compare October 21, 2024 21:57
@renovate renovate bot force-pushed the renovate/major-semantic-release branch from 28b2323 to df4679a Compare October 28, 2024 20:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants