Bump scality/metadata from 8.11.0-standalone to 8.25.0-standalone in /.github/docker

[dependabot]

Bumps scality/metadata from 8.11.0-standalone to 8.25.0-standalone.

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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @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)

[bert-e]

Hello dependabot[bot],

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options

name	description	privileged	authored
/after_pull_request	Wait for the given pull request id to be merged before continuing with the current one.
/bypass_author_approval	Bypass the pull request author's approval	⭐
/bypass_build_status	Bypass the build and test status	⭐
/bypass_commit_size	Bypass the check on the size of the changeset TBA	⭐
/bypass_incompatible_branch	Bypass the check on the source branch prefix	⭐
/bypass_jira_check	Bypass the Jira issue check	⭐
/bypass_peer_approval	Bypass the pull request peers' approval	⭐
/bypass_leader_approval	Bypass the pull request leaders' approval	⭐
/approve	Instruct Bert-E that the author has approved the pull request.		✍️
/create_pull_requests	Allow the creation of integration pull requests.
/create_integration_branches	Allow the creation of integration branches.
/no_octopus	Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
/unanimity	Change review acceptance criteria from one reviewer at least to all reviewers
/wait	Instruct Bert-E not to run until further notice.

Available commands

name	description	privileged
/help	Print Bert-E's manual in the pull request.
/status	Print Bert-E's current status in the pull request TBA
/clear	Remove all comments from Bert-E from the history TBA
/retry	Re-start a fresh build TBA
/build	Re-start a fresh build TBA
/force_reset	Delete integration branches & pull requests, and restart merge process from the beginning.
/reset	Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

The following options are set: bypass_author_approval, bypass_jira_check

[bert-e]

Request integration branches

Waiting for integration branch creation to be requested by the user.

To request integration branches, please comment on this pull request with the following command:

/create_integration_branches

Alternatively, the /approve and /create_pull_requests commands will automatically
create the integration branches.

The following options are set: bypass_author_approval, bypass_jira_check

[codecov]

❌ 1 Tests Failed:

Tests completed	Failed	Passed	Skipped
8298	1	8297	0

View the full list of 1 ❄️ flaky test(s)

should create a bunch of objects and their versions::put and head object with versioning With v4 signature on versioning suspended then enabled bucket w/ null version should create a bunch of objects and their versions

Flake rate in main: 13.81% (Passed 668 times, Failed 107 times)

Stack Traces | 600s run time

Timeout of 600000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (.../test/versioning/objectHead.js)

To view more test analytics, go to the Test Analytics Dashboard
_{📋 Got 3 mins? Take this short survey to help us improve Test Analytics.}

[github-actions]

Dependency Bump Evaluation

Version change: scality/metadata 8.11.0-standalone -> 8.25.0-standalone
Semver bump type: minor (spans 14 minor versions)

Changes:

• Updates the metadata-standalone Docker image in .github/docker/docker-compose.yaml
• This image is used only in CI for SSE KMS migration tests and healthcheck functional tests
• Release notes are unavailable (private repository)

Breaking changes: Unable to determine — the scality/metadata repository is private and release notes/changelogs are not accessible. The jump spans 14 minor versions (8.12.0 through 8.25.0), any of which could include breaking API changes.

Security concerns: Low risk — this is an internal Scality image from ghcr.io/scality/metadata, used only in CI infrastructure, not deployed in production.

Impact on codebase: The metadata-standalone service is consumed as an external network service in CI docker-compose. CloudServer communicates with it via network protocol. No source code changes are needed for this bump. Unit tests, lint, and CodeQL checks have passed. The build check is still in progress.

Recommendation: REVIEW REQUIRED

Notes:

• The 14-minor-version jump (8.11.0 → 8.25.0) warrants verification that the metadata service API contract remains compatible
• A team member with access to the scality/metadata repo should review the intermediate release notes for breaking changes
• Once the build CI check completes and functional tests pass (especially SSE KMS migration and healthcheck tests), this provides strong signal that the bump is safe
• If functional tests pass, this is likely safe to merge

— Claude Code