build(deps): bump quarkus.platform.version from 3.2.9.Final to 3.2.12.Final #410
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
dependabot
bot
added
chore
github-actions
bot
added
the
needs-triage
|
@dependabot rebase |
Bumps `quarkus.platform.version` from 3.2.9.Final to 3.2.12.Final. Updates `io.quarkus.platform:quarkus-bom` from 3.2.9.Final to 3.2.12.Final - [Commits](quarkusio/quarkus-platform@3.2.9.Final...3.2.12.Final) Updates `io.quarkus.platform:quarkus-amazon-services-bom` from 3.2.9.Final to 3.2.12.Final - [Commits](quarkusio/quarkus-platform@3.2.9.Final...3.2.12.Final) Updates `io.quarkus:quarkus-panache-common` from 3.2.9.Final to 3.2.12.Final Updates `io.quarkus.platform:quarkus-maven-plugin` from 3.2.9.Final to 3.2.12.Final - [Commits](quarkusio/quarkus-platform@3.2.9.Final...3.2.12.Final) --- updated-dependencies: - dependency-name: io.quarkus.platform:quarkus-bom dependency-type: direct:production update-type: version-update:semver-patch - dependency-name: io.quarkus.platform:quarkus-amazon-services-bom dependency-type: direct:production update-type: version-update:semver-patch - dependency-name: io.quarkus:quarkus-panache-common dependency-type: direct:production update-type: version-update:semver-patch - dependency-name: io.quarkus.platform:quarkus-maven-plugin dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
force-pushed
the
dependabot/maven/quarkus.platform.version-3.2.12.Final
branch
from
e29da29 to
f6ccb9f
Compare
|
/build_test |
|
Workflow started at 4/30/2024, 9:14:05 AM. View Actions Run. |
|
CI build and push: At least one test failed ❌ (JDK17) |
|
Testing it locally now. The CI failure doesn't really reveal much about what actually went wrong, it just looks like the application doesn't respond at all. |
|
Not sure what's happening. I ran a local build skipping tests and then spun up the smoketest, and that failed to come up because the container health check also indicated that the Cryostat container was not responding. Its logs don't note anything unusual. |
so it's just the latest 3.2.12 that has some issue. |
|
Ah, the Netty versions are out of sync. I bet that's it. |
|
/build_test |
|
Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id> |
3.2.12 should be bringing in Vertx 4.4.9 and Netty 4.1.108. |
|
Workflow started at 4/30/2024, 9:46:11 AM. View Actions Run. |
|
No GraphQL schema changes detected. |
|
No OpenAPI schema changes detected. |
|
CI build and push: All tests pass ✅ (JDK17) |
dependabot
bot
deleted the
dependabot/maven/quarkus.platform.version-3.2.12.Final
branch
Bumps
quarkus.platform.versionfrom 3.2.9.Final to 3.2.12.Final.Updates
io.quarkus.platform:quarkus-bomfrom 3.2.9.Final to 3.2.12.FinalCommits
c556d61[maven-release-plugin] prepare release 3.2.12.Final0ae834fMerge pull request #1181 from aloubyansky/quarkus-3.2.12.Final8c46898Upgrade to Quarkus 3.2.12.Final876b8c4[maven-release-plugin] prepare for next development iterationa93918e[maven-release-plugin] prepare release 3.2.11.Final1c658d0Merge pull request #1146 from aloubyansky/quarkus-3.2.11.Final7db694bUpgrade to Quarkus 3.2.11.Finalc6ede85Merge pull request #1115 from qosdk-bot/qosdk-release-6.3.62ad8addUpdate QOSDK to 6.3.683f10f0Merge pull request #1137 from gsmet/3.2-ci-fixUpdates
io.quarkus.platform:quarkus-amazon-services-bomfrom 3.2.9.Final to 3.2.12.FinalCommits
c556d61[maven-release-plugin] prepare release 3.2.12.Final0ae834fMerge pull request #1181 from aloubyansky/quarkus-3.2.12.Final8c46898Upgrade to Quarkus 3.2.12.Final876b8c4[maven-release-plugin] prepare for next development iterationa93918e[maven-release-plugin] prepare release 3.2.11.Final1c658d0Merge pull request #1146 from aloubyansky/quarkus-3.2.11.Final7db694bUpgrade to Quarkus 3.2.11.Finalc6ede85Merge pull request #1115 from qosdk-bot/qosdk-release-6.3.62ad8addUpdate QOSDK to 6.3.683f10f0Merge pull request #1137 from gsmet/3.2-ci-fixUpdates
io.quarkus:quarkus-panache-commonfrom 3.2.9.Final to 3.2.12.FinalUpdates
io.quarkus.platform:quarkus-maven-pluginfrom 3.2.9.Final to 3.2.12.FinalCommits
c556d61[maven-release-plugin] prepare release 3.2.12.Final0ae834fMerge pull request #1181 from aloubyansky/quarkus-3.2.12.Final8c46898Upgrade to Quarkus 3.2.12.Final876b8c4[maven-release-plugin] prepare for next development iterationa93918e[maven-release-plugin] prepare release 3.2.11.Final1c658d0Merge pull request #1146 from aloubyansky/quarkus-3.2.11.Final7db694bUpgrade to Quarkus 3.2.11.Finalc6ede85Merge pull request #1115 from qosdk-bot/qosdk-release-6.3.62ad8addUpdate QOSDK to 6.3.683f10f0Merge pull request #1137 from gsmet/3.2-ci-fixDependabot 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)