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

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

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jan 11, 2020

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
semantic-release 15.14.0 -> 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)

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 channel (for example.{"channels":[null,"channel1","channel2"]})
      • Push the tags and notes
      • Update the GitHub releases that refer to a tag formatted as v{version}@​{channel} to use the tag without it
      • Delete the tags formatted as v{version}@​{channel}
  • Require Node.js >= 10.13

  • Git CLI version 2.7.1 or higher is now required: The --merge option of the git tag command has been added in Git version 2.7.1 and is now used by semantic-release

  • Regexp are not supported anymore for property matching in the releaseRules option.

    Regex are replaced by globs. For example /core-.*/ should be changed to 'core-*'.

  • The branch option has been removed in favor of branches

  • The new branches option expect either an Array or a single branch definition. To migrate your configuration:

    • If you want to publish package from multiple branches, please see the configuration documentation
    • If you use the default configuration and want to publish only from master: nothing to change
    • If you use the branch configuration and want to publish only from one bra

Configuration

📅 Schedule: Branch creation - "every weekend" in timezone America/New_York, 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 force-pushed the renovate/major-semantic-release-monorepo branch from a96339b to 48a9f4d Compare January 18, 2020 05:09
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 37a218f to cf16f65 Compare February 1, 2020 05:08
@renovate renovate bot changed the title Update dependency semantic-release to v16 Update dependency semantic-release to v17 Feb 1, 2020
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from cf16f65 to 3f00c21 Compare February 15, 2020 05:08
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 3f00c21 to 15d88a5 Compare April 26, 2020 07:59
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 15d88a5 to fce4f1d Compare July 5, 2020 23:04
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from fce4f1d to d8a02a2 Compare January 10, 2021 17:50
@renovate renovate bot changed the title Update dependency semantic-release to v17 chore(deps): update dependency semantic-release to v17 Jan 10, 2021
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from d8a02a2 to 5757a49 Compare February 13, 2021 06:24
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from dd09046 to 87d5eb5 Compare March 6, 2021 05:16
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 87d5eb5 to 7165ca7 Compare March 13, 2021 06:29
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 7165ca7 to 5a26675 Compare May 15, 2021 20:58
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 5a26675 to 0402477 Compare March 26, 2022 15:20
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v17 chore(deps): update dependency semantic-release to v19 Mar 26, 2022
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 0402477 to 74e0c83 Compare June 18, 2022 16:15
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 74e0c83 to 9ea3340 Compare September 25, 2022 16:13
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 9ea3340 to 22a8960 Compare November 20, 2022 17:58
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 22a8960 to a6f08f8 Compare March 25, 2023 05:59
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v19 chore(deps): update dependency semantic-release to v21 Mar 25, 2023
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v21 chore(deps): update dependency semantic-release to v21 - autoclosed Apr 4, 2023
@renovate renovate bot closed this Apr 4, 2023
@renovate renovate bot deleted the renovate/major-semantic-release-monorepo branch April 4, 2023 00:26
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v21 - autoclosed chore(deps): update dependency semantic-release to v21 Apr 4, 2023
@renovate renovate bot reopened this Apr 4, 2023
@renovate renovate bot restored the renovate/major-semantic-release-monorepo branch April 4, 2023 10:02
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from d36f8a1 to bc542f6 Compare June 3, 2023 04:24
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from bc542f6 to c579103 Compare June 10, 2023 06:46
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v21 chore(deps): update dependency semantic-release to v22 Sep 16, 2023
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 4e12475 to 7f2b123 Compare September 23, 2023 06:54
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 7f2b123 to 684991a Compare September 24, 2023 18:53
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 684991a to 0d1f93b Compare November 4, 2023 07:20
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 0d1f93b to f955807 Compare November 18, 2023 07:41
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from f955807 to 006cf85 Compare December 9, 2023 06:20
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 006cf85 to 5251dd6 Compare December 16, 2023 07:43
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 5251dd6 to 1682122 Compare January 13, 2024 06:35
@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 from 1682122 to cfb66db Compare February 10, 2024 07:55
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from 865f7a3 to 4d79951 Compare March 23, 2024 04:34
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 4d79951 to d25772a Compare March 24, 2024 17:19
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from c267883 to 6159155 Compare April 13, 2024 05:46
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 6159155 to cf1a8c6 Compare May 11, 2024 07:21
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from cf1a8c6 to 13b3205 Compare June 1, 2024 07:19
@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 13b3205 to bfff524 Compare August 17, 2024 13:49
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from bfff524 to e42c963 Compare September 14, 2024 04:39
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from e42c963 to 4ba1dd1 Compare September 28, 2024 06:21
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 4ba1dd1 to ffe1fe5 Compare October 19, 2024 06:25
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from ffe1fe5 to 775585a Compare October 26, 2024 06:38
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v24 chore(deps): update dependency semantic-release to v24 - autoclosed Dec 8, 2024
@renovate renovate bot closed this Dec 8, 2024
@renovate renovate bot deleted the renovate/major-semantic-release-monorepo branch December 8, 2024 18:47
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v24 - autoclosed chore(deps): update dependency semantic-release to v24 Dec 14, 2024
@renovate renovate bot reopened this Dec 14, 2024
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