Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Feature/merge 129.0.0 beta.1 tag #4491

Merged
merged 2 commits into from
Dec 3, 2024
Merged

Feature/merge 129.0.0 beta.1 tag #4491

merged 2 commits into from
Dec 3, 2024

Conversation

eg-ayoub
Copy link
Contributor

@eg-ayoub eg-ayoub commented Dec 3, 2024

No description provided.

eg-ayoub added 2 commits December 3, 2024 10:09
Release 129.0.0-beta.1
8c01a43
Merge tag '129.0.0-beta.1' into release/merge-129.0.0-beta.1-tag
d7ebb7b 
MetalK8s 129.0.0-beta.1
===

MetalK8s 129.0.0-beta.1 embeds Kubernetes 1.29.8.

Useful links
---

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

What's new
===

- [
-   "Bump cert-manager chart to 0.16.1",
-   "Bump dex chart to 0.19.1",
-   "Bump fluent-bit chart to 3.1.9",
-   "Bump kube-prometheus-stack chart to 65.3.1",
-   "Bump prometheus-adapter chart to 4.11.0",
-   "Bump nginx image to 1.27.2",
-   "Use rocky minimal images in salt-master and metalk8s-utils",
-   "Bump ingress-inginx chart to 4.11.3",
-   "Bump alpine image to 3.20.3",
-   "Bump operator-sdk to 1.37.0",
-   "Bump loki chart to 6.20.0"
- ]
@bert-e
Copy link
Contributor

bert-e commented Dec 3, 2024

Hello eg-ayoub,

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.

@eg-ayoub
Copy link
Contributor Author

eg-ayoub commented Dec 3, 2024

/approve

@bert-e
Copy link
Contributor

bert-e commented Dec 3, 2024

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:

@bert-e
Copy link
Contributor

bert-e commented Dec 3, 2024

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

vdaviot
vdaviot approved these changes Dec 3, 2024
View reviewed changes
Copy link

@vdaviot vdaviot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Un TL;DR de pourquoi ca passait pas sur le PR précedente ?

@bert-e
Copy link
Contributor

bert-e commented Dec 3, 2024

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

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

The following options are set: approve

@bert-e bert-e merged commit d7ebb7b into development/129.0 Dec 3, 2024
21 checks passed
@bert-e bert-e deleted the feature/merge-129.0.0-beta.1-tag branch December 3, 2024 15:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@TeddyAndrieux TeddyAndrieux TeddyAndrieux approved these changes

@vdaviot vdaviot vdaviot approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@eg-ayoub @bert-e @vdaviot @TeddyAndrieux