-
Notifications
You must be signed in to change notification settings - Fork 55
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
Fix stable branches being tagged as the current #492
Conversation
release. [noissue]
Backport to 3.22: 💚 backport PR created✅ Backport PR branch: Backported as #493 🤖 @patchback |
Fix stable branches being tagged as the current (cherry picked from commit bed07a1)
Backport to 3.25: 💚 backport PR created✅ Backport PR branch: Backported as #494 🤖 @patchback |
Fix stable branches being tagged as the current (cherry picked from commit bed07a1)
Backport to 3.24: 💚 backport PR created✅ Backport PR branch: Backported as #495 🤖 @patchback |
Fix stable branches being tagged as the current (cherry picked from commit bed07a1)
Backport to 3.23: 💚 backport PR created✅ Backport PR branch: Backported as #496 🤖 @patchback |
Fix stable branches being tagged as the current (cherry picked from commit bed07a1)
…a86a9abb969c4204d96f1fec892f33/pr-492 [PR #492/bed07a1b backport][3.25] Fix stable branches being tagged as the current
…a86a9abb969c4204d96f1fec892f33/pr-492 [PR #492/bed07a1b backport][3.23] Fix stable branches being tagged as the current
…a86a9abb969c4204d96f1fec892f33/pr-492 [PR #492/bed07a1b backport][3.24] Fix stable branches being tagged as the current
…a86a9abb969c4204d96f1fec892f33/pr-492 [PR #492/bed07a1b backport][3.22] Fix stable branches being tagged as the current
release.
[noissue]