Skip to content

chore(release-3.6.x): release 3.6.10 - #21380

Merged
spiridonov merged 2 commits into
release-3.6.xfrom
release-please--branches--release-3.6.x
Apr 3, 2026
Merged

chore(release-3.6.x): release 3.6.10#21380
spiridonov merged 2 commits into
release-3.6.xfrom
release-please--branches--release-3.6.x

Conversation

@loki-gh-app

@loki-gh-app loki-gh-app Bot commented Apr 2, 2026

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

3.6.10

3.6.10 (2026-04-02)

Bug Fixes


Merging this PR will release the artifacts of 4a27a08

@loki-gh-app loki-gh-app Bot added autorelease: pending backport main Tag a PR with this label to create a PR which cherry pics it into the main branch product-approved labels Apr 2, 2026
@loki-gh-app
loki-gh-app Bot requested a review from a team as a code owner April 2, 2026 19:09
@loki-gh-app loki-gh-app Bot added backport main Tag a PR with this label to create a PR which cherry pics it into the main branch product-approved autorelease: pending labels Apr 2, 2026
@loki-gh-app
loki-gh-app Bot force-pushed the release-please--branches--release-3.6.x branch from 11bd12a to 53d91f7 Compare April 2, 2026 20:24
@pull-request-size pull-request-size Bot added size/L and removed size/XS labels Apr 2, 2026
Signed-off-by: Stas Spiridonov <stanislav@spiridonov.pro>
@pull-request-size pull-request-size Bot added size/XS and removed size/L labels Apr 3, 2026
@spiridonov
spiridonov enabled auto-merge (squash) April 3, 2026 15:32
@spiridonov
spiridonov merged commit dba9f7c into release-3.6.x Apr 3, 2026
80 checks passed
@spiridonov
spiridonov deleted the release-please--branches--release-3.6.x branch April 3, 2026 15:32
@loki-gh-app

loki-gh-app Bot commented Apr 3, 2026

Copy link
Copy Markdown
Contributor Author

The backport to main failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new branch
git switch --create backport-21380-to-main origin/main
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x dba9f7c38ed4a8b639252656e029641020211f04

When the conflicts are resolved, stage and commit the changes:

git add . && git cherry-pick --continue

If you have the GitHub CLI installed:

# Push the branch to GitHub:
git push --set-upstream origin backport-21380-to-main
# Create the PR body template
PR_BODY=$(gh pr view 21380 --json body --template 'Backport dba9f7c38ed4a8b639252656e029641020211f04 from #21380{{ "\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.10 (backport main)' --body-file - --label 'size/XS' --label 'product-approved' --label 'autorelease: pending' --label 'backport' --base main --milestone main --web

Or, 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-21380-to-main

# Create a pull request where the `base` branch is `main` and the `compare`/`head` branch is `backport-21380-to-main`.

# Remove the local backport branch
git switch main
git branch -D backport-21380-to-main
@loki-gh-app

loki-gh-app Bot commented Apr 3, 2026

Copy link
Copy Markdown
Contributor Author
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

autorelease: tagged backport main Tag a PR with this label to create a PR which cherry pics it into the main branch backport-failed product-approved size/XS

1 participant