-
Notifications
You must be signed in to change notification settings - Fork 33
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
Future Release Branches Frozen For Merging | branch:release-4.18 branch:release-4.19 #218
Labels
tide/merge-blocker
Denotes an issue that blocks the tide merge queue for a branch while it is open.
Comments
openshift-merge-robot
added
the
tide/merge-blocker
Denotes an issue that blocks the tide merge queue for a branch while it is open.
label
Apr 19, 2024
openshift-merge-robot
changed the title
Future Release Branches Frozen For Merging | branch:release-4.16 branch:release-4.17
Future Release Branches Frozen For Merging | branch:release-4.17
May 17, 2024
openshift-merge-robot
changed the title
Future Release Branches Frozen For Merging | branch:release-4.17
Future Release Branches Frozen For Merging | branch:release-4.17 branch:release-4.18
May 23, 2024
openshift-merge-robot
changed the title
Future Release Branches Frozen For Merging | branch:release-4.17 branch:release-4.18
Future Release Branches Frozen For Merging | branch:release-4.18
Aug 9, 2024
openshift-merge-robot
changed the title
Future Release Branches Frozen For Merging | branch:release-4.18
Future Release Branches Frozen For Merging | branch:release-4.18 branch:release-4.19
Aug 13, 2024
MaysaMacedo
pushed a commit
to shiftstack/csi-operator
that referenced
this issue
Sep 16, 2024
STOR-1688: Chore: add .snyk file to ignore false positives
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
tide/merge-blocker
Denotes an issue that blocks the tide merge queue for a branch while it is open.
The following branches are being fast-forwarded from the current development branch (master) as placeholders for future releases. No merging is allowed into these release branches until they are unfrozen for production release.
release-4.18
release-4.19
For more information, see the branching documentation.
The text was updated successfully, but these errors were encountered: