chore(deps-dev): bump semantic-release and gradle-semantic-release-plugin #121
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
…ugin Bumps [semantic-release](https://github.com/semantic-release/semantic-release) and [gradle-semantic-release-plugin](https://github.com/KengoTODA/gradle-semantic-release-plugin). These dependencies needed to be updated together. Updates `semantic-release` from 19.0.5 to 20.1.1 - [Release notes](https://github.com/semantic-release/semantic-release/releases) - [Commits](semantic-release/semantic-release@v19.0.5...v20.1.1) Updates `gradle-semantic-release-plugin` from 1.7.4 to 1.7.6 - [Release notes](https://github.com/KengoTODA/gradle-semantic-release-plugin/releases) - [Changelog](https://github.com/KengoTODA/gradle-semantic-release-plugin/blob/master/CHANGELOG.md) - [Commits](KengoTODA/gradle-semantic-release-plugin@v1.7.4...v1.7.6) --- updated-dependencies: - dependency-name: semantic-release dependency-type: direct:development update-type: version-update:semver-major - dependency-name: gradle-semantic-release-plugin dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
dependencies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bumps semantic-release and gradle-semantic-release-plugin. These dependencies needed to be updated together.
Updates
semantic-releasefrom 19.0.5 to 20.1.1Release notes
Sourced from semantic-release's releases.
... (truncated)
Commits
31d9bfefix(deps): update dependency execa to v7 (#2709)7bbaaf9chore(deps): update dependency ava to v5.2.0 (#2702)42b67ceci: set test workflow timeout to 10 minutes (#2720)f991a59test(integration): fix package name conflict (#2719)1775ed8docs(extending): add link to semantic-release-coralogix (#2710)1beeb84build(deps): bump http-cache-semantics from 4.1.0 to 4.1.1d170f73feat(plugins): add support for loading ESM plugins (#2688)5df624cfix(windows): fixed issues preventing execution from windows (#2672)914b0a2Revert "chore(deps): update dependency ava to v5.1.1" (#2682)140e36ddocs(workflow-configuration): improved sentence structure (#2679)Updates
gradle-semantic-release-pluginfrom 1.7.4 to 1.7.6Release notes
Sourced from gradle-semantic-release-plugin's releases.
Changelog
Sourced from gradle-semantic-release-plugin's changelog.
Commits
e01458echore(release): 1.7.6 [skip ci]d46d759docs: happy new year 2023!aa339a0fix: bump up promisified-properties to 2.0.27ddea8e3ci: do not need to use PR-target event to build this package681aadbchore(release): 1.7.5 [skip ci]4998da8ci: use Node 18 to run the buildb567057fix: support semantic-release v20 that requires Node v189fe5d0fchore(deps-dev): bump typescript from 4.9.3 to 4.9.4e64c97fchore(dev-deps): bump json5 from 2.2.0 to 2.2.3 (#503)6f6ad27chore(deps-dev): bump husky from 8.0.2 to 8.0.3Dependabot 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)