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

[dependabot]

Bumps scality/vault from 7.76.0 to 7.89.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]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 84.58%. Comparing base (33ae58e) to head (01bc05b).
✅ All tests successful. No failed tests found.

Additional details and impacted files

see 2 files with indirect coverage changes

@@                 Coverage Diff                 @@
##           development/9.3    #6171      +/-   ##
===================================================
- Coverage            84.60%   84.58%   -0.02%     
===================================================
  Files                  206      206              
  Lines                13358    13358              
===================================================
- Hits                 11301    11299       -2     
- Misses                2057     2059       +2     

Flag	Coverage Δ
file-ft-tests	68.34% <ø> (-0.06%)	⬇️
kmip-ft-tests	28.31% <ø> (ø)
mongo-v0-ft-tests	69.54% <ø> (-0.10%)	⬇️
mongo-v1-ft-tests	69.59% <ø> (-0.02%)	⬇️
multiple-backend	36.79% <ø> (ø)
sur-tests	35.85% <ø> (-0.83%)	⬇️
sur-tests-inflights	37.67% <ø> (-0.06%)	⬇️
unit	70.50% <ø> (ø)
utapi-v2-tests	34.56% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[github-actions]

Dependency Bump Evaluation

Version change: scality/vault 7.76.0 -> 7.89.0 (Docker image)
Semver bump type: Minor (13 minor versions)

Changes:

• Updates the vault Docker image tag in .github/docker/docker-compose.yaml (CI test infrastructure only)
• Vault is used as the IAM/auth backend during integration tests with the vault docker-compose profile
• SSE migration tests in tests.yaml use separate hardcoded vault images (7.70.31/7.70.32) and are NOT affected

Breaking changes: Unable to verify — scality/vault is a private repository and release notes for versions 7.77.0 through 7.89.0 are not accessible. The 13 minor version jump warrants manual review of the vault changelog.

Security concerns: Vault handles IAM authentication, credentials, and authorization. While this is a test-only image, compatibility with the auth code paths in lib/auth/vault.js should be verified.

Impact on codebase: No source code changes — only the CI Docker image tag is updated. However, a vault API or behavior change could cause integration test failures.

CI Status: prettier check FAILED on .github/docker/docker-compose.yaml — the file has formatting issues that must be resolved before merge. Other checks (unit tests, lint, codecov) passed. Build and CodeQL were still in progress.

Recommendation: REVIEW REQUIRED

Notes:

1. The prettier CI failure must be fixed first (run prettier --write on the docker-compose.yaml)
2. A team member with access to the vault repo should review the changelog for versions 7.77.0–7.89.0 to check for breaking API changes
3. Once CI is green, running the vault-profile integration tests would confirm compatibility

— Claude Code