Skip to content

Bump release to 5.4.0 #510

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

Merged
merged 1 commit into from
Feb 18, 2025
Merged

Bump release to 5.4.0 #510

merged 1 commit into from
Feb 18, 2025

Conversation

inknos
Copy link
Contributor

@inknos inknos commented Feb 12, 2025

No description provided.

Copy link
Contributor

openshift-ci bot commented Feb 12, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: inknos

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@inknos
Copy link
Contributor Author

inknos commented Feb 12, 2025

/packit test

@inknos
Copy link
Contributor Author

inknos commented Feb 13, 2025

@jwhonce PTAL

we see the infinite job flake again but the tests are passing

@inknos inknos force-pushed the 5.4.0 branch 9 times, most recently from f63eff2 to c1e5e69 Compare February 18, 2025 15:28
Signed-off-by: Nicola Sella <[email protected]>
@jwhonce
Copy link
Member

jwhonce commented Feb 18, 2025

LGTM

Copy link
Member

@Luap99 Luap99 left a comment

Choose a reason for hiding this comment

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

just as general feedback as you have asked for a review, I cannot follow any of the changes besides the obvious version number changes.

I at least would think the github action fix and tmt change must in a separate commit and explain why these are changes are made in the commit message. Like this I have no idea why they are needed, there is no link to an issue, etc... And if someone goes back later and git blame points we at something like that I would have nothing to go by why this was done.

Now I do so that the indentation in the github action but simply saying this int he commit message goes a long way for a reviewer like me.
Anyway I am not a maintainer here so merge if you like.

@TomSweeneyRedHat
Copy link
Member

LGTM
I will second @Luap99 on the version being in it's own commit. Please do that going forward.

@TomSweeneyRedHat
Copy link
Member

/lgtm

@openshift-ci openshift-ci bot added the lgtm label Feb 18, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 371bec7 into containers:main Feb 18, 2025
25 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants