Skip to content

Merge release tag for 129.0.0#4532

Merged
bert-e merged 2 commits intodevelopment/129.0from
feature/merge-129.0.0-tag
Mar 10, 2025
Merged

Merge release tag for 129.0.0#4532
bert-e merged 2 commits intodevelopment/129.0from
feature/merge-129.0.0-tag

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

No description provided.

eg-ayoub added 2 commits March 10, 2025 09:43
MetalK8s 129.0.0
===

MetalK8s 129.0.0 embeds Kubernetes 1.29.8.

Useful links
---

- [Documentation](https://metal-k8s.readthedocs.io/en/129.0.0)
- [Upgrade notes](https://metal-k8s.readthedocs.io/en/129.0.0/operation/upgrade.html)
- [Changelog](https://github.com/scality/metalk8s/blob/129.0.0/CHANGELOG.md)

What's new
===

- Drop RHEL 7 based OS support
- Add cert-manager
- Bump Kubernetes version to 1.29.8
- Bump ETCD version to 3.5.15
- Bump containerd version to 1.6.36
- Bump all addons
@github-actions
Copy link
Copy Markdown
Contributor Author

/approve

@github-actions github-actions bot requested a review from a team as a code owner March 10, 2025 09:43
@bert-e
Copy link
Copy Markdown
Contributor

bert-e commented Mar 10, 2025

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

bert-e commented Mar 10, 2025

Conflict

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

I have not created the integration branch.

Here are the steps to resolve this conflict:

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

The following options are set: approve, bypass_author_approval, bypass_jira_check

@bert-e
Copy link
Copy Markdown
Contributor

bert-e commented Mar 10, 2025

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

@bert-e
Copy link
Copy Markdown
Contributor

bert-e commented Mar 10, 2025

Build failed

The build for commit did not succeed in branch feature/merge-129.0.0-tag

The following options are set: approve, bypass_author_approval, bypass_jira_check

@bert-e
Copy link
Copy Markdown
Contributor

bert-e commented Mar 10, 2025

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

  • ✔️ development/129.0

  • ✔️ development/130.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/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-129.

Goodbye github-actions[bot].

The following options are set: approve, bypass_author_approval, bypass_jira_check

@bert-e bert-e merged commit 20ce874 into development/129.0 Mar 10, 2025
22 checks passed
@bert-e bert-e deleted the feature/merge-129.0.0-tag branch March 10, 2025 23:34
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.

2 participants