chore(release-3.6.x): release 3.6.11 - #21485
Merged
sandeepsukhani merged 1 commit intoMay 13, 2026
Merged
Conversation
loki-gh-app
Bot
force-pushed
the
release-please--branches--release-3.6.x
branch
2 times, most recently
from
April 9, 2026 14:11
9b6c8d8 to
ba88805
Compare
loki-gh-app
Bot
force-pushed
the
release-please--branches--release-3.6.x
branch
from
May 13, 2026 08:43
ba88805 to
ce66d83
Compare
sandeepsukhani
approved these changes
May 13, 2026
Contributor
Author
|
The backport to To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new branch
git switch --create backport-21485-to-main origin/main
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x 69ba8d8f8bf5f506e59a5dcf7e0fdf25c9bf200eWhen the conflicts are resolved, stage and commit the changes: If you have the GitHub CLI installed: # Push the branch to GitHub:
git push --set-upstream origin backport-21485-to-main
# Create the PR body template
PR_BODY=$(gh pr view 21485 --json body --template 'Backport 69ba8d8f8bf5f506e59a5dcf7e0fdf25c9bf200e from #21485{{ "\n\n---\n\n" }}{{ index . "body" }}')
# Create the PR on GitHub
echo "${PR_BODY}" | gh pr create --title 'chore(release-3.6.x): release 3.6.11 (backport main)' --body-file - --label 'size/S' --label 'product-approved' --label 'autorelease: pending' --label 'backport' --base main --milestone main --webOr, if you don't have the GitHub CLI installed (we recommend you install it!): # Push the branch to GitHub:
git push --set-upstream origin backport-21485-to-main
# Create a pull request where the `base` branch is `main` and the `compare`/`head` branch is `backport-21485-to-main`.
# Remove the local backport branch
git switch main
git branch -D backport-21485-to-main |
Contributor
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 I have created a release beep boop
3.6.11
3.6.11 (2026-05-13)
Bug Fixes
Merging this PR will release the artifacts of f7a4aa9