Skip to content

Bump scality/vault from 7.76.0 to 7.87.0 in /.github/docker#6161

Open
dependabot[bot] wants to merge 1 commit intodevelopment/9.3from
dependabot/docker_compose/dot-github/docker/scality/vault-7.87.0
Open

Bump scality/vault from 7.76.0 to 7.87.0 in /.github/docker#6161
dependabot[bot] wants to merge 1 commit intodevelopment/9.3from
dependabot/docker_compose/dot-github/docker/scality/vault-7.87.0

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github Apr 25, 2026

Bumps scality/vault from 7.76.0 to 7.87.0.

Dependabot compatibility score

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)

Bumps scality/vault from 7.76.0 to 7.87.0.

---
updated-dependencies:
- dependency-name: scality/vault
  dependency-version: 7.87.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file docker_compose Pull requests that update docker_compose code labels Apr 25, 2026
@bert-e
Copy link
Copy Markdown
Contributor

bert-e commented Apr 25, 2026

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
Copy link
Copy Markdown
Contributor

bert-e commented Apr 25, 2026

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
Copy link
Copy Markdown

codecov Bot commented Apr 25, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 84.44%. Comparing base (bb5ca88) to head (430cb10).
✅ All tests successful. No failed tests found.

Additional details and impacted files

Impacted file tree graph
see 3 files with indirect coverage changes

@@                 Coverage Diff                 @@
##           development/9.3    #6161      +/-   ##
===================================================
- Coverage            84.45%   84.44%   -0.01%     
===================================================
  Files                  206      206              
  Lines                13307    13307              
===================================================
- Hits                 11238    11237       -1     
- Misses                2069     2070       +1     
Flag Coverage Δ
file-ft-tests 67.95% <ø> (ø)
kmip-ft-tests 28.12% <ø> (-0.04%) ⬇️
mongo-v0-ft-tests 69.11% <ø> (-0.10%) ⬇️
mongo-v1-ft-tests 69.11% <ø> (-0.12%) ⬇️
multiple-backend 36.33% <ø> (ø)
sur-tests 35.59% <ø> (-0.04%) ⬇️
sur-tests-inflights 37.43% <ø> (-0.04%) ⬇️
unit 70.16% <ø> (ø)
utapi-v2-tests 34.35% <ø> (ø)

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.

Copy link
Copy Markdown

@github-actions github-actions Bot left a comment

Choose a reason for hiding this comment

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

Dependency Bump Evaluation

Version change: 7.76.0 -> 7.87.0 (minor, 11 versions)
Bump type: Docker image tag (ghcr.io/scality/vault) in CI docker-compose
Breaking changes: None identified
Security concerns: None — Docker image swap only, no new transitive deps. Vault handles auth (sensitive path), but client interface is stable and version-locked (vaultclient@8.5.3)

CI status: lint, unit-tests, dependency-review, codecov, alert-tests passed. Build and CodeQL still in progress at time of review.

Impact on codebase: No code changes. Vault is used only in CI for S3C functional tests (S3VAULT=scality). CloudServer communicates via vaultclient@8.5.3 through stable API interfaces (account management, authentication, KMS). The Docker image is activated only under the vault compose profile.

Release notes: Unavailable (private repository) — unable to inspect intermediate releases for breaking changes.

Recommendation: SAFE TO MERGE

Notes:

  • Minor version bump within major version 7 — backward compatibility expected
  • Dependabot config already blocks major version bumps for scality/vault (manual review required)
  • Confirm S3C functional tests pass once the build job completes

— Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file docker_compose Pull requests that update docker_compose code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant