chore(deps): bump the docker-compose-images group in /release/conformance/openid with 2 updates - #564
Conversation
Bumps the docker-compose-images group in /release/conformance/openid with 2 updates: maven and mongo. Updates `maven` from 3-eclipse-temurin-21 to 3-eclipse-temurin-26 Updates `mongo` from 6.0.13 to 8.2.12 --- updated-dependencies: - dependency-name: maven dependency-version: 3-eclipse-temurin-26 dependency-type: direct:production dependency-group: docker-compose-images - dependency-name: mongo dependency-version: 8.2.12 dependency-type: direct:production update-type: version-update:semver-major dependency-group: docker-compose-images ... Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4872b517c3
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| services: | ||
| builder: | ||
| image: maven:3-eclipse-temurin-21@sha256:2b4496088e7b80ae10a8c9f74e574ea21380325a006ec684532ad6bad5bc7273 | ||
| image: maven:3-eclipse-temurin-26@sha256:d5617b9a6307e1b51dc7c55edf09bacb66f1c91fb861949c34a3a0d4e16bd241 |
There was a problem hiding this comment.
Keep the builder Java pin aligned with CI
For this release-area change, the documented release source check includes python3 -m unittest release/scripts/test_openid_conformance_runner.py, and that suite currently has test_builder_override_pins_maven_image_by_digest asserting the builder override stays on maven:3-eclipse-temurin-21@sha256:. Changing this line to Temurin 26 makes that required check fail immediately; keep the builder on the expected JDK 21 pin or update the runner/test contract together if the suite is intentionally moving Java levels.
AGENTS.md reference: AGENTS.md:L56-L60
Useful? React with 👍 / 👎.
| services: | ||
| builder: | ||
| image: maven:3-eclipse-temurin-21@sha256:2b4496088e7b80ae10a8c9f74e574ea21380325a006ec684532ad6bad5bc7273 | ||
| image: maven:3-eclipse-temurin-26@sha256:d5617b9a6307e1b51dc7c55edf09bacb66f1c91fb861949c34a3a0d4e16bd241 |
There was a problem hiding this comment.
Keep the builder Java pin aligned with CI
For this release-area change, the documented release source check includes python3 -m unittest release/scripts/test_openid_conformance_runner.py, and that suite currently has test_builder_override_pins_maven_image_by_digest asserting the builder override stays on maven:3-eclipse-temurin-21@sha256:. Changing this line to Temurin 26 makes that required check fail immediately; keep the builder on the expected JDK 21 pin or update the runner/test contract together if the suite is intentionally moving Java levels.
Useful? React with 👍 / 👎.
| services: | ||
| mongodb: | ||
| image: mongo:6.0.13@sha256:b415b12f638e2685d06c58ab7fb5943577c50fadec6d9340ef67d21aeac72070 | ||
| image: mongo:8.2.12@sha256:e0ce8c35124d4a9f9785532d1f268f39e9728ffa1cb38f46fa482436424c4bd3 |
There was a problem hiding this comment.
Avoid jumping persisted Mongo data straight to 8.2
When an operator reuses the default conformance checkout after any prior run, the pinned upstream compose file’s ./mongo/data:/data/db bind mount preserves Mongo 6.0 data across down, but this override now starts that same data directory with Mongo 8.2. MongoDB’s standalone 8.2 upgrade guide says existing deployments must already be 8.0-series and earlier versions must be upgraded successively, so the suite can fail to start until the local data is manually deleted or migrated; either keep this on 6.0/perform a supported intermediate upgrade, or make the runner clear/migrate the ignored data directory for this major bump. See upstream compose and MongoDB’s upgrade path docs: https://raw.githubusercontent.com/openid-certification/conformance-suite/dee9a25160e789f0f80517674693ef7989ab9fa1/docker-compose.yml and https://www.mongodb.com/docs/manual/release-notes/8.2-upgrade-standalone/.
Useful? React with 👍 / 👎.
| services: | ||
| builder: | ||
| image: maven:3-eclipse-temurin-21@sha256:2b4496088e7b80ae10a8c9f74e574ea21380325a006ec684532ad6bad5bc7273 | ||
| image: maven:3-eclipse-temurin-26@sha256:d5617b9a6307e1b51dc7c55edf09bacb66f1c91fb861949c34a3a0d4e16bd241 |
There was a problem hiding this comment.
This commit has no Signed-off-by: trailer, and the repository’s DCO workflow checks every non-merge commit in the PR range and exits nonzero when that trailer is absent. Please amend/recreate the commit with git commit -s so the DCO gate can pass.
Useful? React with 👍 / 👎.
Bumps the docker-compose-images group in /release/conformance/openid with 2 updates: maven and mongo.
Updates
mavenfrom 3-eclipse-temurin-21 to 3-eclipse-temurin-26Updates
mongofrom 6.0.13 to 8.2.12Dependabot 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 show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions