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 v23 #188

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 18, 2021

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
semantic-release 17.4.7 -> 23.1.1 age adoption passing confidence

Release Notes

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

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


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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v18 chore(deps): update dependency semantic-release to v19 Mar 26, 2022
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from e5f0f06 to 1be0cbe Compare March 26, 2022 15:45
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 1be0cbe to 3a1387c Compare September 25, 2022 19:41
@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 force-pushed the renovate/major-semantic-release-monorepo branch from 3a1387c to bc40864 Compare March 25, 2023 05:13
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from eb2f592 to cf1df1c Compare June 3, 2023 04:14
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from cf1df1c to c84ca66 Compare June 10, 2023 04:14
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from c84ca66 to 6cd7f5e Compare July 1, 2023 06:03
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 6cd7f5e to d85d1a6 Compare July 8, 2023 06:50
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 6649ccc to 1628e56 Compare August 26, 2023 05:14
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 1628e56 to 58dbccc Compare September 16, 2023 06:11
@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 25c2b5d to f53a11c Compare September 23, 2023 04:37
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from f53a11c to e9fd04b Compare September 24, 2023 18:46
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from e9fd04b to 53673eb Compare November 4, 2023 06:41
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 53673eb to 3e2da89 Compare November 18, 2023 06:04
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from f00c362 to 3fa2ad6 Compare December 16, 2023 06:48
@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 3fa2ad6 to 83f4ea9 Compare January 13, 2024 07:43
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 83f4ea9 to 4f3769c Compare February 10, 2024 07:39
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 14f935e to 038ddc3 Compare March 23, 2024 04:03
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 038ddc3 to 4c7d354 Compare March 24, 2024 20:20
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 4c7d354 to a5e66ed Compare April 6, 2024 05:29
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from a5e66ed to 912463d Compare April 13, 2024 04:50
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 912463d to f702ba9 Compare May 11, 2024 07:32
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.

None yet

0 participants