Merge release tag for 131.0.0-alpha.7 #4672

github-actions · 2025-10-08T22:05:45Z

No description provided.

github-actions · 2025-10-08T22:05:45Z

/approve

bert-e · 2025-10-08T22:05:49Z

Hello github-actions[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 · 2025-10-08T22:05:55Z

Integration data created

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

this pull request will merge feature/merge-131.0.0-alpha.7-tag into
development/131.0
w/132.0/feature/merge-131.0.0-alpha.7-tag will be merged into development/132.0

The following branches will NOT be impacted:

development/123.0
development/124.0
development/124.1
development/125.0
development/126.0
development/127.0
development/128.0
development/129.0
development/130.0
development/2.0
development/2.1
development/2.10
development/2.11
development/2.2
development/2.3
development/2.4
development/2.5
development/2.6
development/2.7
development/2.8
development/2.9

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: approve, bypass_author_approval, bypass_jira_check

bert-e · 2025-10-08T22:05:57Z

Waiting for approval

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

the author
one peer

Peer approvals must include at least 1 approval from the following list:

The following options are set: approve, bypass_author_approval, bypass_jira_check

MetalK8s 131.0.0-alpha.7 === MetalK8s 131.0.0-alpha.7 embeds Kubernetes 1.31.10. Useful links --- - [Documentation](https://metal-k8s.readthedocs.io/en/131.0.0-alpha.7) - [Upgrade notes](https://metal-k8s.readthedocs.io/en/131.0.0-alpha.7/operation/upgrade.html) - [Changelog](https://github.com/scality/metalk8s/blob/131.0.0-alpha.7/CHANGELOG.md)

bert-e · 2025-12-05T18:28:45Z

History mismatch

Merge commit #f24bb6a09aaceaa280ec32cd7291378cfe8721c6 on the integration branch
w/132.0/feature/merge-131.0.0-alpha.7-tag is merging a branch which is neither the current
branch feature/merge-131.0.0-alpha.7-tag nor the development branch
development/132.0.

It is likely due to a rebase of the branch feature/merge-131.0.0-alpha.7-tag and the
merge is not possible until all related w/* branches are deleted or updated.

Please use the reset command to have me reinitialize these branches.

The following options are set: approve, bypass_author_approval, bypass_jira_check

TeddyAndrieux · 2025-12-05T18:29:03Z

/reset

bert-e · 2025-12-05T18:29:14Z

Reset complete

I have successfully deleted this pull request's integration branches.

The following options are set: approve, bypass_author_approval, bypass_jira_check

bert-e · 2025-12-05T18:29:23Z

Integration data created

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

this pull request will merge feature/merge-131.0.0-alpha.7-tag into
development/131.0
w/132.0/feature/merge-131.0.0-alpha.7-tag will be merged into development/132.0

The following branches will NOT be impacted:

development/123.0
development/124.0
development/124.1
development/125.0
development/126.0
development/127.0
development/128.0
development/129.0
development/130.0
development/2.0
development/2.1
development/2.10
development/2.11
development/2.2
development/2.3
development/2.4
development/2.5
development/2.6
development/2.7
development/2.8
development/2.9

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: approve, bypass_author_approval, bypass_jira_check

bert-e · 2025-12-05T18:35:33Z

In the queue

The changeset has received all authorizations and has been added to the
relevant queue(s). The queue(s) will be merged in the target development
branch(es) as soon as builds have passed.

The changeset will be merged in:

✔️ development/131.0
✔️ development/132.0

The following branches will NOT be impacted:

development/123.0
development/124.0
development/124.1
development/125.0
development/126.0
development/127.0
development/128.0
development/129.0
development/130.0
development/2.0
development/2.1
development/2.10
development/2.11
development/2.2
development/2.3
development/2.4
development/2.5
development/2.6
development/2.7
development/2.8
development/2.9

There is no action required on your side. You will be notified here once
the changeset has been merged. In the unlikely event that the changeset
fails permanently on the queue, a member of the admin team will
contact you to help resolve the matter.

IMPORTANT

Please do not attempt to modify this pull request.

Any commit you add on the source branch will trigger a new cycle after the
current queue is merged.
Any commit you add on one of the integration branches will be lost.

If you need this pull request to be removed from the queue, please contact a
member of the admin team now.

The following options are set: approve, bypass_author_approval, bypass_jira_check

bert-e · 2025-12-05T18:42:49Z

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

✔️ development/131.0
✔️ development/132.0

The following branches have NOT changed:

development/123.0
development/124.0
development/124.1
development/125.0
development/126.0
development/127.0
development/128.0
development/129.0
development/130.0
development/2.0
development/2.1
development/2.10
development/2.11
development/2.2
development/2.3
development/2.4
development/2.5
development/2.6
development/2.7
development/2.8
development/2.9

Please check the status of the associated issue MERGE-131.

Goodbye github-actions[bot].

Release 131.0.0-alpha.7

08f05d4

TeddyAndrieux force-pushed the feature/merge-131.0.0-alpha.7-tag branch from f24bb6a to 5aaf915 Compare December 5, 2025 18:28

TeddyAndrieux approved these changes Dec 5, 2025

View reviewed changes

bert-e merged commit 9e85c60 into development/131.0 Dec 5, 2025
22 checks passed

bert-e deleted the feature/merge-131.0.0-alpha.7-tag branch December 5, 2025 18:42

bert-e restored the feature/merge-131.0.0-alpha.7-tag branch December 5, 2025 18:42

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Merge release tag for 131.0.0-alpha.7 #4672

Merge release tag for 131.0.0-alpha.7 #4672

Uh oh!

github-actions bot commented Oct 8, 2025

Uh oh!

github-actions bot commented Oct 8, 2025

Uh oh!

bert-e commented Oct 8, 2025

Uh oh!

bert-e commented Oct 8, 2025

Uh oh!

bert-e commented Oct 8, 2025

Uh oh!

bert-e commented Dec 5, 2025

Uh oh!

TeddyAndrieux commented Dec 5, 2025

Uh oh!

bert-e commented Dec 5, 2025

Uh oh!

bert-e commented Dec 5, 2025

Uh oh!

bert-e commented Dec 5, 2025

Uh oh!

bert-e commented Dec 5, 2025

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Merge release tag for 131.0.0-alpha.7 #4672

Merge release tag for 131.0.0-alpha.7 #4672

Uh oh!

Conversation

github-actions bot commented Oct 8, 2025

Uh oh!

github-actions bot commented Oct 8, 2025

Uh oh!

bert-e commented Oct 8, 2025

Hello github-actions[bot],

Uh oh!

bert-e commented Oct 8, 2025

Integration data created

Uh oh!

bert-e commented Oct 8, 2025

Waiting for approval

Uh oh!

bert-e commented Dec 5, 2025

History mismatch

Uh oh!

TeddyAndrieux commented Dec 5, 2025

Uh oh!

bert-e commented Dec 5, 2025

Reset complete

Uh oh!

bert-e commented Dec 5, 2025

Integration data created

Uh oh!

bert-e commented Dec 5, 2025

In the queue

Uh oh!

bert-e commented Dec 5, 2025

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants