Merge release tag for 131.0.0 #4683

github-actions · 2025-10-22T15:16:44Z

No description provided.

MetalK8s 131.0.0 === MetalK8s 131.0.0 embeds Kubernetes 1.31.10. Useful links --- - [Documentation](https://metal-k8s.readthedocs.io/en/131.0.0) - [Upgrade notes](https://metal-k8s.readthedocs.io/en/131.0.0/operation/upgrade.html) - [Changelog](https://github.com/scality/metalk8s/blob/131.0.0/CHANGELOG.md) What's new === - Improved Data Visualization on Dashboard page - Introduced an UI Operator to manage Micro-Application deployment - Bump Kubernetes to 1.31.0

github-actions · 2025-10-22T15:16:45Z

/approve

bert-e · 2025-10-22T15:16:50Z

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-22T15:17:12Z

Conflict

A conflict has been raised during the creation of
integration branch w/132.0/feature/merge-131.0.0-tag with contents from feature/merge-131.0.0-tag
and development/132.0.

I have not created the integration branch.

Here are the steps to resolve this conflict:

 git fetch
 git checkout -B w/132.0/feature/merge-131.0.0-tag origin/development/132.0
 git merge origin/feature/merge-131.0.0-tag
 # <intense conflict resolution>
 git commit
 git push -u origin w/132.0/feature/merge-131.0.0-tag

The following options are set: approve, bypass_author_approval, bypass_jira_check

ChengYanJin · 2025-10-29T15:19:06Z

/status

bert-e · 2025-10-29T15:19:11Z

Status

Status report is not available.

The following options are set: approve, bypass_author_approval, bypass_jira_check

bert-e · 2025-10-29T16:19:20Z

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-10-29T19:03:22Z

Queue build failed

The corresponding build for the queue failed:

Checkout the status page.
Identify the failing build and review the logs.
If no issue is found, re-run the build.
If an issue is identified, checkout the steps below to remove
the pull request from the queue for further analysis and maybe rebase/merge.

Remove the pull request from the queue

Add a /wait comment on this pull request.
Click on login on the status page.
Go into the manage page.
Find the option called Rebuild the queue and click on it.
Bert-E will loop again on all pull requests to put the valid ones
in the queue again, while skipping the one with the /wait comment.
Wait for the new queue to merge, then merge/rebase your pull request
with the latest changes to then work on a proper fix.
Once the issue is fixed, delete the /wait comment and
follow the usual process to merge the pull request.

ziyang-lin-404 · 2025-10-30T09:22:04Z

/status

bert-e · 2025-10-30T09:22:09Z

Status

Status report is not available.

The following options are set: approve, bypass_author_approval, bypass_jira_check

bert-e · 2025-10-30T09:22:31Z

Queue build failed

The corresponding build for the queue failed:

Checkout the status page.
Identify the failing build and review the logs.
If no issue is found, re-run the build.
If an issue is identified, checkout the steps below to remove
the pull request from the queue for further analysis and maybe rebase/merge.

Remove the pull request from the queue

Add a /wait comment on this pull request.
Click on login on the status page.
Go into the manage page.
Find the option called Rebuild the queue and click on it.
Bert-E will loop again on all pull requests to put the valid ones
in the queue again, while skipping the one with the /wait comment.
Wait for the new queue to merge, then merge/rebase your pull request
with the latest changes to then work on a proper fix.
Once the issue is fixed, delete the /wait comment and
follow the usual process to merge the pull request.

bert-e · 2025-10-30T10:52:53Z

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].

JeanMarcMilletScality added 2 commits October 22, 2025 15:16

Release 131.0.0

8f998ba

github-actions bot requested a review from a team as a code owner October 22, 2025 15:16

JBWatenbergScality approved these changes Oct 29, 2025

View reviewed changes

bert-e merged commit 594c1e1 into development/131.0 Oct 30, 2025
46 of 47 checks passed

bert-e deleted the feature/merge-131.0.0-tag branch October 30, 2025 10:52

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Merge release tag for 131.0.0 #4683

Merge release tag for 131.0.0 #4683

Uh oh!

github-actions bot commented Oct 22, 2025

Uh oh!

github-actions bot commented Oct 22, 2025

Uh oh!

bert-e commented Oct 22, 2025

Uh oh!

bert-e commented Oct 22, 2025

Uh oh!

ChengYanJin commented Oct 29, 2025

Uh oh!

bert-e commented Oct 29, 2025

Uh oh!

bert-e commented Oct 29, 2025

Uh oh!

bert-e commented Oct 29, 2025

Uh oh!

ziyang-lin-404 commented Oct 30, 2025

Uh oh!

bert-e commented Oct 30, 2025

Uh oh!

bert-e commented Oct 30, 2025

Uh oh!

bert-e commented Oct 30, 2025

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

Merge release tag for 131.0.0 #4683

Merge release tag for 131.0.0 #4683

Uh oh!

Conversation

github-actions bot commented Oct 22, 2025

Uh oh!

github-actions bot commented Oct 22, 2025

Uh oh!

bert-e commented Oct 22, 2025

Hello github-actions[bot],

Uh oh!

bert-e commented Oct 22, 2025

Conflict

Uh oh!

ChengYanJin commented Oct 29, 2025

Uh oh!

bert-e commented Oct 29, 2025

Status

Uh oh!

bert-e commented Oct 29, 2025

In the queue

Uh oh!

bert-e commented Oct 29, 2025

Queue build failed

Uh oh!

ziyang-lin-404 commented Oct 30, 2025

Uh oh!

bert-e commented Oct 30, 2025

Status

Uh oh!

bert-e commented Oct 30, 2025

Queue build failed

Uh oh!

bert-e commented Oct 30, 2025

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants