Skip to content

build(deps): Bump the docker-compose-images group in /release/conformance/openid with 2 updates #376

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.

Sign up for GitHub

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

Closed
dependabot wants to merge 1 commit into from
+2 −2
Closed

build(deps): Bump the docker-compose-images group in /release/conformance/openid with 2 updates #376

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion release/conformance/openid/docker-compose-builder.override.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
services:
builder:
image: maven:3-eclipse-temurin-21@sha256:2b4496088e7b80ae10a8c9f74e574ea21380325a006ec684532ad6bad5bc7273
image: maven:3-eclipse-temurin-26@sha256:d5617b9a6307e1b51dc7c55edf09bacb66f1c91fb861949c34a3a0d4e16bd241

@chatgpt-codex-connector chatgpt-codex-connector Bot Jul 16, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Fix the broken conformance runner test

With this image changed to maven:3-eclipse-temurin-26, the documented release check python3 -m unittest release/scripts/test_openid_conformance_runner.py now fails because release/scripts/test_openid_conformance_runner.py:69 still asserts that the builder override contains maven:3-eclipse-temurin-21@sha256:. This leaves the release/conformance gate red for this dependency bump; update the test's reviewed pin expectation alongside the image or keep the Maven pin at 21.

Useful? React with 👍 / 👎.

2 changes: 1 addition & 1 deletion release/conformance/openid/docker-compose.override.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
services:
mongodb:
image: mongo:6.0.13@sha256:b415b12f638e2685d06c58ab7fb5943577c50fadec6d9340ef67d21aeac72070
image: mongo:8.2.11@sha256:951c2ff9fc6bdb6cb89b1dfea4a0e8ae3ee4fb287c0bf579b2bba54c7803f75d

@chatgpt-codex-connector chatgpt-codex-connector Bot Jul 16, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Avoid stranding existing Mongo 6 data directories

When a developer has already run the conformance suite with the previous mongo:6.0.13 pin, the pinned upstream compose bind-mounts ./mongo/data:/data/db under the reused suite checkout, so this direct jump to Mongo 8.2 will try to open persisted 6.0 files. MongoDB's 8.0 standalone upgrade guide says a 6.0-series deployment must upgrade to 7.0 before 8.0 (https://www.mongodb.com/docs/manual/release-notes/8.0-upgrade-standalone/#upgrade-version-path), so openid-conformance-runner.py up can fail for existing workspaces unless the runner purges/renames the old data directory or the bump is staged through a compatible upgrade path.

Useful? React with 👍 / 👎.

nginx:
build:
context: ./nginx
Expand Down
Loading