-
Notifications
You must be signed in to change notification settings - Fork 17
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
Bump org.openrewrite.recipe:rewrite-recipe-bom from 2.10.0 to 2.12.0 #172
Bump org.openrewrite.recipe:rewrite-recipe-bom from 2.10.0 to 2.12.0 #172
Conversation
Saving others a click by reporting the failure here
Looks like this first popped up in this version bump:
There's not a lot of changes between the affected OpenRewrite versions, but one stands out
Is there any reason why there might be a duplicate recipe ID here? Anything in the generator perhaps? /cc @gsmet (no rush) |
Looks like this line needs to be changed, as it redefines
|
Yeah, will fix it. Thanks for raising the issue. |
Bumps [org.openrewrite.recipe:rewrite-recipe-bom](https://github.com/openrewrite/rewrite-recipe-bom) from 2.10.0 to 2.12.0. - [Release notes](https://github.com/openrewrite/rewrite-recipe-bom/releases) - [Commits](openrewrite/rewrite-recipe-bom@v2.10.0...v2.12.0) --- updated-dependencies: - dependency-name: org.openrewrite.recipe:rewrite-recipe-bom dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
f6e7266
to
9d05658
Compare
Uncovered the next one:
|
9d05658
to
59934b4
Compare
@timtebeek FWIW, we still get the warnings about the failing Maven repos when running our test suite. |
Bumps org.openrewrite.recipe:rewrite-recipe-bom from 2.10.0 to 2.12.0.
Release notes
Sourced from org.openrewrite.recipe:rewrite-recipe-bom's releases.
Commits
bdf1296
Merge pull request #27 from openrewrite/refactor/update-gradle-wrapper55f6cb8
refactor: Update Gradle wrapper37aa445
Gradle Enterprise -> Develocity3eb016c
Drop rewrite-cloud-suitability-analyzerc13a444
Add rewrite-jacksonDependabot 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)