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.

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

Merge release tag for 128.0.2 #4505

Open
wants to merge 2 commits into
base: development/128.0
Choose a base branch
from

Conversation

github-actions[bot]
Copy link

No description provided.

eg-ayoub added 2 commits December 26, 2024 14:42
MetalK8s 128.0.2
===

MetalK8s 128.0.2 is a patch release (see [the main release 128.0.0](https://github.com/scality/metalk8s/releases/128.0.0)).

Useful links
---

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

What's new
===

- First iteration ingress hardening
- disable grafana dashboard for loki if disabled
@github-actions github-actions bot requested a review from a team as a code owner December 26, 2024 14:42
Copy link
Author

/approve

@bert-e
Copy link
Contributor

bert-e commented Dec 26, 2024

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
Contributor

bert-e commented Dec 26, 2024

Conflict

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

I have not created the integration branch.

Here are the steps to resolve this conflict:

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

The following options are set: approve, bypass_author_approval, bypass_jira_check

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.

1 participant