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

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 5, 2021

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
semantic-release 15.14.0 -> 24.2.3 age adoption passing confidence

Release Notes

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

v24.2.3

Compare Source

Bug Fixes

v24.2.2

Compare Source

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.

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)

v19.0.5

Compare Source

Reverts

v19.0.4

Compare Source

Bug Fixes

v19.0.3

Compare Source

Bug Fixes
  • log-repo: use the original form of the repo url to remove the need to mask credentials (#​2459) (58a226f), closes #​2449

v19.0.2

Compare Source

Bug Fixes
  • npm-plugin: upgraded to the stable version (0eca144)

v19.0.1

Compare Source

Bug Fixes
  • npm-plugin: upgraded to the latest beta version (8097afb)

v19.0.0

Compare Source

Bug Fixes
  • npm-plugin: upgraded to the beta, which upgrades npm to v8 (f634b8c)
  • upgrade marked to resolve ReDos vulnerability (#​2330) (d9e5bc0)
BREAKING CHANGES
  • npm-plugin: @semantic-release/npm has also dropped support for node v15
  • node v15 has been removed from our defined supported versions of node. this was done to upgrade to compatible versions of marked and marked-terminal that resolved the ReDoS vulnerability. removal of support of this node version should be low since it was not an LTS version and has been EOL for several months already.

v18.0.1

Compare Source

Bug Fixes

v18.0.0

Compare Source

This is a maintenance release. An increasing amount of dependencies required a node version higher than the Node 10 version supported by semantic-release@17. We decided to go straight to a recent Node LTS version because the release build is usually independent of others, requiring a higher node version is less disruptive to users, but helps us reduce the maintenance overhead.

If you use GitHub Actions and need to bump the node version set up by actions/node-setup, you can use octoherd-script-bump-node-version-in-workflows

BREAKING CHANGES

node-version: the minimum required version of node is now v14.17

v17.4.7

Compare Source

Bug Fixes
  • engines: fixed defined node version to account for the higher requirement from the npm plugin (#​2088) (ea52e17)

v17.4.6

Compare Source

Bug Fixes

v17.4.5

Compare Source

Bug Fixes
  • deps: update dependency marked to v3 (6e4beb8)

v17.4.4

Compare Source

Bug Fixes

v17.4.3

Compare Source

Bug Fixes
  • bump minimal version of lodash to address CVE-2021-23337 (#​1931) (55194c1)

v17.4.2

Compare Source

Bug Fixes

v17.4.1

Compare Source

Bug Fixes

v17.4.0

Compare Source

Features

v17.3.9

Compare Source

Bug Fixes

v17.3.8

Compare Source

Bug Fixes
  • deps: update dependency marked to v2 (a2eaed0)

v17.3.7

Compare Source

Bug Fixes

v17.3.6

Compare Source

Bug Fixes

v17.3.5

Compare Source

Bug Fixes

v17.3.4

Compare Source

Bug Fixes

v17.3.3

Compare Source

Bug Fixes

v17.3.2

Compare Source

Bug Fixes

v17.3.1

Compare Source

Bug Fixes

v17.3.0

Compare Source

Features

v17.2.4

Compare Source

Bug Fixes

v17.2.3

Compare Source

Bug Fixes
  • mask secrets when characters get uri encoded (ca90b34)

v17.2.2

Compare Source

Bug Fixes
  • don't parse port as part of the path in repository URLs (#​1671) (77a75f0)
  • use valid git credentials when multiple are provided (#​1669) (2bf3771)

v17.2.1

Compare Source

Reverts

v17.2.0

Compare Source

Features
  • throw an Error if package.json has duplicate "repository" key (#​1656) (b8fb35c)

v17.1.2

Compare Source

Bug Fixes

v17.1.1

Compare Source

Bug Fixes

v17.1.0

Compare Source

Features
  • bitbucket-basic-auth: support for bitbucket server basic auth (#​1578) (a465801)

v17.0.8

Compare Source

Bug Fixes
  • prevent false positive secret replacement for Golang projects (#​1562) (eed1d3c)

v17.0.7

Compare Source

Bug Fixes

v17.0.6

Compare Source

Bug Fixes

v17.0.5

Compare Source

Bug Fixes
  • adapt for semver to version 7.3.2 (0363790)

v17.0.4

Compare Source

Bug Fixes
  • add repositoryUrl in logs (55be0ba)

v17.0.3

Compare Source

Bug Fixes
  • pass a branch name to getGitAuthUrl (e7bede1)

v17.0.2

Compare Source

Bug Fixes
  • package: update marked-terminal to version 4.0.0 (8ce2d6e)

v17.0.1

Compare Source

Bug Fixes

v17.0.0

Compare Source

BREAKING CHANGES
  • Require Node.js >= 10.18

v16.0.4

Compare Source

Bug Fixes
  • correct error when remote repository has no branches (c6b1076)

v16.0.3

Compare Source

Bug Fixes
  • use --no-verify when testing the Git permissions (b54b20d)

v16.0.2

Compare Source

Bug Fixes
  • fetch tags on repo cached by the CI (6b5b02e)

v16.0.1

Compare Source

Bug Fixes
  • package: update env-ci to version 5.0.0 (3739ab5)

v16.0.0

Compare Source

BREAKING CHANGES
  • ⚠️ For v16.0.0@​beta users only:

    In v16, a JSON object stored in a Git note is used to keep track of the channels on which a version has been released, the @{channel} suffix is no longer necessary.

    The tags formatted as v{version}@​{channel} will now be ignored. If you have releases using this format you will have to upgrade them:

    • Find all the versions that have been released on a branch other than the default one by searching for all tags formatted as v{version}@​{channel}
    • For each of those version:
      • Create a tag without the {@​channel} if none doesn't already exists
      • Add a Git note to the tag without the {@​channel} containing the channels on which the version was released formatted as {"channels":["channel1","channel2"]} and using null for the default cha

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.

🔕 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 from 9242e3f to d0926ee Compare January 24, 2021 12:54
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 7 times, most recently from a02217d to 4d4df6c Compare February 13, 2021 08:08
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from d48c495 to 6f3a7ae Compare March 3, 2021 22:41
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 6f3a7ae to 496124b Compare March 11, 2021 20:36
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 496124b to 04e3c5b Compare May 15, 2021 19:10
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 04e3c5b to a471046 Compare October 19, 2021 01:29
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v17 chore(deps): update dependency semantic-release to v18 Oct 19, 2021
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from a471046 to 15ff92e Compare March 7, 2022 11:01
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v18 chore(deps): update dependency semantic-release to v19 Mar 7, 2022
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 15ff92e to 6b0743d Compare June 18, 2022 20:15
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 6b0743d to dbe640b Compare November 20, 2022 20:27
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v19 chore(deps): update dependency semantic-release to v20 Mar 17, 2023
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from dbe640b to 42022b0 Compare March 17, 2023 04:07
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 42022b0 to 318ca3d Compare March 24, 2023 23:27
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v20 chore(deps): update dependency semantic-release to v21 Mar 24, 2023
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 318ca3d to 18476df Compare April 3, 2023 11:08
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from e6c5089 to 550fd10 Compare June 2, 2023 22:35
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 9a1d425 to b7baded Compare June 10, 2023 01:21
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from b7baded to cadf757 Compare June 29, 2023 00:38
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 36ae8ea to 31c9d47 Compare August 20, 2023 04:56
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 159c002 to f0fd0fc Compare September 24, 2023 18:25
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from e4bc913 to edfc504 Compare November 3, 2023 22:41
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from edfc504 to d92bbef Compare November 17, 2023 02:20
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from cdeeb5f to 3af5964 Compare December 12, 2023 00:12
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 3af5964 to 5724c8d Compare December 12, 2023 07:48
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 5724c8d to e29a6b1 Compare January 13, 2024 00:30
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v22 chore(deps): update dependency semantic-release to v23 Jan 13, 2024
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 6ea0252 to 099fea1 Compare February 7, 2024 15:21
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 9885caf to 529284f Compare March 18, 2024 15:19
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 529284f to b31e5d5 Compare March 24, 2024 16:50
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from dd36c9c to 991646a Compare April 9, 2024 21:44
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 991646a to 88dff88 Compare May 10, 2024 19:44
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 88dff88 to 14c724d Compare June 1, 2024 02:22
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v23 chore(deps): update dependency semantic-release to v24 Jun 1, 2024
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 14c724d to 59761ee Compare August 17, 2024 13:27
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 59761ee to dae0a63 Compare September 11, 2024 04:51
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from dae0a63 to 633c661 Compare September 27, 2024 19:27
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 7d5b676 to 6c205e6 Compare October 25, 2024 19:54
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 6c205e6 to e3e2060 Compare January 3, 2025 05:11
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from e3e2060 to d759686 Compare February 9, 2025 15:38
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from d759686 to 30a8479 Compare February 15, 2025 20:34
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.

0 participants