chore(deps): bump com.spotify.fmt:fmt-maven-plugin from 2.22.1 to 2.27 in /sdk/java#1049
Conversation
Bumps [com.spotify.fmt:fmt-maven-plugin](https://github.com/spotify/fmt-maven-plugin) from 2.22.1 to 2.27. - [Release notes](https://github.com/spotify/fmt-maven-plugin/releases) - [Commits](spotify/fmt-maven-plugin@2.22.1...2.27.0) --- updated-dependencies: - dependency-name: com.spotify.fmt:fmt-maven-plugin dependency-version: '2.27' dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
|
This PR is stale because it has been open 14 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
|
This PR was closed because it has been stalled for 7 days with no activity. |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
dependabot
bot
deleted the
dependabot/maven/sdk/java/com.spotify.fmt-fmt-maven-plugin-2.27
branch
Bumps com.spotify.fmt:fmt-maven-plugin from 2.22.1 to 2.27.
Release notes
Sourced from com.spotify.fmt:fmt-maven-plugin's releases.
Commits
7370aa9[maven-release-plugin] prepare release 2.27.02a6bcc0[maven-release-plugin] prepare for next development iteration4e1fd13Upgrade Google Java Format 1.24.0 -> 1.26.0 (#198)e139c6eUpdate workflow with new versions (#201)8b68c45[maven-release-plugin] prepare for next development iteration9e0190f[maven-release-plugin] prepare release 2.25a3aff4aUpgrade Google Java Format 1.23.0 -> 1.24.0 (#194)7fa55be[maven-release-plugin] prepare for next development iterationf5a2675[maven-release-plugin] prepare release 2.24775d418Upgrade Google Java Format 1.22.0 -> 1.23.0 (#192)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 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 show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@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)