Bump scality/vault from 7.76.0 to 7.88.0 in /.github/docker

[dependabot]

Bumps scality/vault from 7.76.0 to 7.88.0.

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
8428	1	8427	0

View the top 1 failed test(s) by shortest run time

"before each" hook for "should retrieve a part put after part copied from MPU"::GET object With v4 signature With PartNumber field uploadPartCopy "before each" hook for "should retrieve a part put after part copied from MPU"

Stack Traces | 5.52s run time

Connection timed out after 5000 ms

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: 7.76.0 -> 7.88.0 (12 minor versions)
Semver bump type: minor

Changes:

• Updates the ghcr.io/scality/vault Docker image tag from 7.76.0 to 7.88.0 in .github/docker/docker-compose.yaml
• Single-line change affecting only the CI/test infrastructure, not production code
• Release notes unavailable (private repository)

Breaking changes: Unable to verify — scality/vault is a private repository and release notes are not accessible. The 12 minor version jump (7.76.0 → 7.88.0) warrants careful review.

Security concerns: Vault is an IAM/authentication service, making it security-sensitive. However, this change only affects the Docker image used in CI tests. The vaultclient npm package (v8.5.3) that cloudserver uses to communicate with vault is unchanged, so the client-side interface remains stable.

Impact on codebase:

• Only .github/docker/docker-compose.yaml is modified (CI infrastructure)
• No production code, no vaultclient version change
• SSE migration tests use their own fixed vault versions (7.70.31 / 7.70.32) and are unaffected
• CloudServer's vault auth layer (lib/auth/vault.js) communicates via vaultclient which is pinned at 8.5.3

Recommendation: REVIEW REQUIRED

Notes:

• The prettier CI check is failing on the changed file (docker-compose.yaml has formatting that doesn't match prettier expectations — likely a pre-existing issue surfaced by the file modification)
• Multiple CI checks (unit-tests, functional tests, SSE migration tests) are still in progress at time of evaluation
• Cannot assess backward compatibility without access to vault release notes spanning 12 minor versions
• Recommend waiting for all CI checks to pass (fixing the prettier formatting issue) before merging
• A team member with access to the vault repository should verify no breaking API changes were introduced between 7.76.0 and 7.88.0

— Claude Code