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

build(deps-dev): Bump semantic-release from 21.1.1 to 22.0.0 #593

Merged

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Sep 18, 2023

Bumps semantic-release from 21.1.1 to 22.0.0.

Release notes

Sourced from semantic-release's releases.

v22.0.0

22.0.0 (2023-09-16)

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

v22.0.0-beta.9

22.0.0-beta.9 (2023-09-16)

Features

  • 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

v22.0.0-beta.8

22.0.0-beta.8 (2023-09-16)

Bug Fixes

  • deps: update dependency aggregate-error to v5 (#2956) (1017e1a)

... (truncated)

Commits
  • 11788ed Merge pull request #2934 from semantic-release/beta
  • b93bef4 feat(node-versions): raised the minimum supported node version w/in the v20 r...
  • 6604153 Merge branch 'master' of github.com:semantic-release/semantic-release into beta
  • e623cc6 feat(node-versions): raised the minimum node v20 requirement to v20.6
  • 42f7b82 chore(deps): update dependency testdouble to v3.19.0 (#2961)
  • 1017e1a fix(deps): update dependency aggregate-error to v5 (#2956)
  • a23b718 fix(deps): upgraded to the latest version of the npm plugin with npm v10
  • fb850ff Merge branch 'master' of github.com:semantic-release/semantic-release into beta
  • b9f294d feat(node-versions): raised the minimum required node version to v18.17 and d...
  • 03a687b fix(deps): updated to the latest beta of the commit analyzer plugin
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [semantic-release](https://github.com/semantic-release/semantic-release) from 21.1.1 to 22.0.0.
- [Release notes](https://github.com/semantic-release/semantic-release/releases)
- [Commits](semantic-release/semantic-release@v21.1.1...v22.0.0)

---
updated-dependencies:
- dependency-name: semantic-release
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Sep 18, 2023
@github-actions github-actions bot enabled auto-merge (squash) September 18, 2023 12:22
@github-actions github-actions bot merged commit 95d3aa9 into main Sep 18, 2023
9 of 11 checks passed
@github-actions github-actions bot deleted the dependabot/npm_and_yarn/main/semantic-release-22.0.0 branch September 18, 2023 12:26
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 javascript Pull requests that update Javascript code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants