Skip to content

Drop the AWS SDK v2 maintenance-message suppression - #2890

Merged
bert-e merged 5 commits into
development/9.6from
improvement/BB-883-drop-aws-sdk-v2-suppression
Oct 16, 2026
Merged

bert-e merged 5 commits into
development/9.6from
improvement/BB-883-drop-aws-sdk-v2-suppression

Conversation

@francoisferrand

@francoisferrand francoisferrand commented Oct 16, 2026 •

Copy link
Copy Markdown
Contributor

We were silencing the AWS SDK v2 maintenance notice in the image because v2 still came in through bucketclient's arsenal. Now that our whole dependency tree runs on SDK v3, the image no longer contains v2 at all, so the workaround can go.

This also moves arsenal from the 8.6.0 preview to the actual release, and bumps cloudserver (used in tests) to 9.5.0, which is built on the same arsenal. That lets us drop a few dependency overrides that only existed to patch packages cloudserver no longer pulls in.

Issue: BB-883

Move off the 8.6.0 preview to the final release. Arsenal 8.6.0 moves its
OpenTelemetry SDK to 0.223, so bump the instrumentations we hand to it
alongside, to keep a single copy of the OTel instrumentation packages in
the image.

Issue: BB-883
The release depends on the released arsenal 8.6.0, so the dev tree no
longer carries a second copy of the 8.6.0 preview.

Issue: BB-883
Arsenal already pulls 2.12.0, so the devDependency resolves to it too.

Issue: BB-883
cloudserver 9.5.0 no longer brings request or oas-tools into the dev
tree, so these overrides match nothing and only left orphaned entries
in the lockfile.

Issue: BB-883
Nothing in the production dependency tree pulls aws-sdk v2 anymore, so
the variable silencing its maintenance-mode notice is no longer needed.

Issue: BB-883
@bert-e

bert-e commented Oct 16, 2026

Copy link
Copy Markdown
Contributor

Hello francoisferrand,

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 ⭐
/bypass_source_branch_lineage Bypass the cross-branch contamination check ⭐
/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.
/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.

@codecov

codecov Bot commented Oct 16, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 81.24%. Comparing base (07fb8f8) to head (64dd89f).
⚠️ Report is 5 commits behind head on development/9.6.

Additional details and impacted files

Impacted file tree graph
see 4 files with indirect coverage changes

Components Coverage Δ
Bucket Notification 85.50% <ø> (ø)
Core Library 86.88% <ø> (-0.39%) ⬇️
Ingestion 83.38% <ø> (ø)
Lifecycle 86.24% <ø> (ø)
Oplog Populator 89.48% <ø> (ø)
Replication 68.64% <ø> (-0.03%) ⬇️
Bucket Scanner 89.37% <ø> (ø)
@@                 Coverage Diff                 @@
##           development/9.6    #2890      +/-   ##
===================================================
- Coverage            81.41%   81.24%   -0.17%     
===================================================
  Files                  209      209              
  Lines                44290    44290              
===================================================
- Hits                 36057    35985      -72     
- Misses                8233     8305      +72     
Flag Coverage Δ
api:retry 14.57% <ø> (ø)
api:routes 14.59% <ø> (ø)
bucket-scanner 89.37% <ø> (ø)
ft_test:queuepopulator 17.36% <ø> (-1.28%) ⬇️
ingestion 20.55% <ø> (ø)
lib 12.90% <ø> (-0.01%) ⬇️
lifecycle 26.78% <ø> (ø)
notification 1.89% <ø> (ø)
oplogPopulator 0.45% <ø> (ø)
replication 25.24% <ø> (-0.01%) ⬇️
unit 67.48% <ø> (ø)

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

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@scality scality deleted a comment from bert-e Oct 16, 2026
@francoisferrand

Copy link
Copy Markdown
Contributor Author

/approve

@bert-e

bert-e commented Oct 16, 2026

Copy link
Copy Markdown
Contributor

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • 2 peers

@bert-e

bert-e commented Oct 16, 2026

Copy link
Copy Markdown
Contributor

I have successfully merged the changeset of this pull request
into targetted development branches:

  • ✔️ development/9.6

The following branches have NOT changed:

  • development/7.10
  • development/7.4
  • development/7.70
  • development/8.6
  • development/9.0
  • development/9.1
  • development/9.2
  • development/9.3
  • development/9.4
  • development/9.5

This pull request did not target the following hotfix branch(es) so they
were left untouched:

  • hotfix/7.10.4
  • hotfix/7.4.4
  • hotfix/7.4.8
  • hotfix/7.4.9
  • hotfix/7.4.6
  • hotfix/7.6.0
  • hotfix/7.10.2
  • hotfix/7.10.17
  • hotfix/7.8.0
  • hotfix/7.10.12
  • hotfix/7.7.0
  • hotfix/9.0.4
  • hotfix/7.4.1
  • hotfix/7.4.5
  • hotfix/7.2.0
  • hotfix/7.70.15
  • hotfix/7.10.3
  • hotfix/7.4.2
  • hotfix/7.4.0
  • hotfix/7.70.1
  • hotfix/7.10.8
  • hotfix/7.70.12
  • hotfix/7.4.10
  • hotfix/7.10.0
  • hotfix/7.4.3
  • hotfix/7.9.0
  • hotfix/7.4.7
  • hotfix/9.0.7
  • hotfix/7.10.1
  • hotfix/8.2.12

Please check the status of the associated issue BB-883.

Goodbye francoisferrand.

The following options are set: approve

@bert-e
bert-e merged commit 64dd89f into development/9.6 Oct 16, 2026
24 checks passed
@bert-e
bert-e deleted the improvement/BB-883-drop-aws-sdk-v2-suppression branch October 16, 2026 18:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants