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 23.0.0 to 23.0.1 #93

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 7, 2024

Bumps semantic-release from 23.0.0 to 23.0.1.

Release notes

Sourced from semantic-release's releases.

v23.0.1

23.0.1 (2024-02-06)

Bug Fixes

  • deps: update dependency marked-terminal to v7 (9faded8)
Commits
  • 9faded8 fix(deps): update dependency marked-terminal to v7
  • fccab39 chore(deps): lock file maintenance (#3179)
  • 6be2280 chore(deps): update dependency got to v14.2.0 (#3175)
  • 518b47d chore(deps): update dependency npm-run-all2 to v6.1.2 (#3171)
  • c6c01aa ci(action): update github/codeql-action action to v3.24.0 (#3173)
  • ee4f99f chore(deps): update dependency ava to v6.1.1 (#3168)
  • 9b9c9b7 chore(deps): update dependency got to v14.1.0 (#3167)
  • 211704d Merge pull request #3166 from knownasnaffy/patch-1
  • 01779f4 docs: fix typo in JS API guide
  • 95ea5ef chore(deps): lock file maintenance (#3165)
  • 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 23.0.0 to 23.0.1.
- [Release notes](https://github.com/semantic-release/semantic-release/releases)
- [Commits](semantic-release/semantic-release@v23.0.0...v23.0.1)

---
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 the dependencies Pull requests that update a dependency file label Feb 7, 2024
@contentful-automation contentful-automation bot merged commit 8d55616 into master Feb 7, 2024
1 of 2 checks passed
@contentful-automation contentful-automation bot deleted the dependabot/npm_and_yarn/semantic-release-23.0.1 branch February 7, 2024 00:38
@contentful-automation
Copy link

🎉 This PR is included in version 3.1.2 🎉

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

Successfully merging this pull request may close these issues.

0 participants