Skip to content

CLDSRV-1021: Bump version to 9.3.29 - #6370

Merged
bert-e merged 1 commit into
development/9.3from
bugfix/CLDSRV-1021-bump-version
Nov 10, 2026
Merged

bert-e merged 1 commit into
development/9.3from
bugfix/CLDSRV-1021-bump-version

Conversation

@tcarmet

@tcarmet tcarmet commented Nov 10, 2026 •

Copy link
Copy Markdown
Contributor

Bump the version for the next releases.

@bert-e

bert-e commented Nov 10, 2026

Copy link
Copy Markdown
Contributor

Hello tcarmet,

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.

@bert-e

bert-e commented Nov 10, 2026

Copy link
Copy Markdown
Contributor

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.

@tcarmet

tcarmet commented Nov 10, 2026

Copy link
Copy Markdown
Contributor Author

/create_integration_branches

@bert-e

bert-e commented Nov 10, 2026

Copy link
Copy Markdown
Contributor

Conflict

A conflict has been raised during the creation of
integration branch w/9.4/bugfix/CLDSRV-1021-bump-version with contents from bugfix/CLDSRV-1021-bump-version
and development/9.4.

I have not created the integration branch.

Here are the steps to resolve this conflict:

 git fetch
 git checkout -B w/9.4/bugfix/CLDSRV-1021-bump-version origin/development/9.4
 git merge origin/bugfix/CLDSRV-1021-bump-version
 # <intense conflict resolution>
 git commit
 git push -u origin w/9.4/bugfix/CLDSRV-1021-bump-version

The following options are set: create_integration_branches

@codecov

codecov Bot commented Nov 10, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 85.38%. Comparing base (06563bd) to head (b6605a1).
⚠️ Report is 1 commits behind head on development/9.3.
✅ All tests successful. No failed tests found.

Additional details and impacted files

Impacted file tree graph
see 4 files with indirect coverage changes

@@                 Coverage Diff                 @@
##           development/9.3    #6370      +/-   ##
===================================================
- Coverage            85.49%   85.38%   -0.11%     
===================================================
  Files                  207      207              
  Lines                13503    13503              
===================================================
- Hits                 11544    11530      -14     
- Misses                1959     1973      +14     
Flag Coverage Δ
file-ft-tests 68.44% <ø> (ø)
file-ft-tests-null-compat 68.95% <ø> (ø)
kmip-ft-tests 28.34% <ø> (ø)
mongo-v0-ft-tests 69.65% <ø> (-0.03%) ⬇️
mongo-v1-ft-tests 69.63% <ø> (-0.07%) ⬇️
multiple-backend 36.81% <ø> (ø)
s3c-ft-tests-v0 64.14% <ø> (ø)
s3c-ft-tests-v0-null-compat 64.20% <ø> (ø)
s3c-ft-tests-v1 64.11% <ø> (ø)
sur-tests 35.93% <ø> (ø)
sur-tests-inflights 37.74% <ø> (ø)
unit 72.02% <ø> (ø)
utapi-v2-tests 34.63% <ø> (-0.03%) ⬇️

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.

@bert-e

bert-e commented Nov 10, 2026

Copy link
Copy Markdown
Contributor

Integration data created

I have created the integration data for the additional destination branches.

The following branches will NOT be impacted:

  • development/7.10
  • development/7.4
  • development/7.70
  • development/8.8
  • development/9.0
  • development/9.1
  • development/9.2

You can set option create_pull_requests if you need me to create
integration pull requests in addition to integration branches, with:

@bert-e create_pull_requests

The following options are set: create_integration_branches

@bert-e

bert-e commented Nov 10, 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

The following options are set: create_integration_branches

@tcarmet
tcarmet requested a review from a team November 10, 2026 21:02
@tcarmet
tcarmet requested a review from a team November 10, 2026 21:08
@tcarmet

tcarmet commented Nov 10, 2026

Copy link
Copy Markdown
Contributor Author

/approve

@bert-e

bert-e commented Nov 10, 2026

Copy link
Copy Markdown
Contributor

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

  • ✔️ development/9.3

  • ✔️ development/9.4

  • ✔️ development/9.5

  • ✔️ development/9.6

The following branches have NOT changed:

  • development/7.10
  • development/7.4
  • development/7.70
  • development/8.8
  • development/9.0
  • development/9.1
  • development/9.2

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

  • hotfix/7.4.5
  • hotfix/9.0.32
  • hotfix/7.70.51
  • hotfix/9.2.36
  • hotfix/7.10.0
  • hotfix/7.10.30
  • hotfix/7.4.3
  • hotfix/9.0.7
  • hotfix/6.4.7
  • hotfix/7.4.2
  • hotfix/7.10.27
  • hotfix/7.7.0
  • hotfix/7.10.3
  • hotfix/7.10.49
  • hotfix/7.10.4
  • hotfix/7.9.0
  • hotfix/7.6.0
  • hotfix/7.70.21
  • hotfix/7.10.28
  • hotfix/7.10.1
  • hotfix/7.4.6
  • hotfix/7.4.1
  • hotfix/7.8.0
  • hotfix/7.4.0
  • hotfix/7.10.2
  • hotfix/7.4.10
  • hotfix/7.2.0
  • hotfix/7.70.73
  • hotfix/7.70.45
  • hotfix/9.2.24
  • hotfix/7.10.15
  • hotfix/8.8.45
  • hotfix/9.3.13
  • hotfix/7.4.4
  • hotfix/7.4.8
  • hotfix/7.4.9
  • hotfix/7.10.8
  • hotfix/7.70.11
  • hotfix/7.4.7

Please check the status of the associated issue CLDSRV-1021.

Goodbye tcarmet.

The following options are set: approve, create_integration_branches

@bert-e
bert-e merged commit b6605a1 into development/9.3 Nov 10, 2026
36 of 37 checks passed
@bert-e
bert-e deleted the bugfix/CLDSRV-1021-bump-version branch November 10, 2026 22:06
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