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-dev): bump semantic-release from 21.0.3 to 21.0.5 #350

Merged

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jun 12, 2023

Bumps semantic-release from 21.0.3 to 21.0.5.

Release notes

Sourced from semantic-release's releases.

v21.0.5

21.0.5 (2023-06-09)

Bug Fixes

  • deps: update dependency marked to v5 (452e1fa)

v21.0.4

21.0.4 (2023-06-09)

Bug Fixes

  • deps: update dependency @​semantic-release/error to v4 (d259350)
Commits
  • 452e1fa fix(deps): update dependency marked to v5
  • 94e773d ci(action): update actions/checkout digest to c85c95e
  • 18730e8 Merge pull request #2826 from semantic-release/renovate/major-semantic-releas...
  • 4bf763f test(semantic-release-error): switched instanceof check to the native version
  • d259350 fix(deps): update dependency @​semantic-release/error to v4
  • 286bd67 chore(deps): lock file maintenance (#2825)
  • 95551a0 chore(deps): update dependency ava to v5.3.0 (#2809)
  • 4e80bab chore(deps): lock file maintenance (#2816)
  • 5145268 chore(deps): update dependency got to v13 (#2813)
  • See full diff 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 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.0.3 to 21.0.5.
- [Release notes](https://github.com/semantic-release/semantic-release/releases)
- [Commits](semantic-release/semantic-release@v21.0.3...v21.0.5)

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

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Jun 12, 2023
@github-actions github-actions bot merged commit 49482fb into main Jun 12, 2023
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/semantic-release-21.0.5 branch June 12, 2023 05:12
@Kampfmoehre
Copy link
Member

🎉 This PR is included in version 1.0.22 🎉

The release is available on:

Your semantic-release bot 📦🚀

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 released
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant