Skip to content

docs: fix upgrade Helm version#20533

Merged
JStickler merged 2 commits intomainfrom
2026.01.21_Upgrade
Jan 21, 2026
Merged

docs: fix upgrade Helm version#20533
JStickler merged 2 commits intomainfrom
2026.01.21_Upgrade

Conversation

@JStickler
Copy link
Copy Markdown
Contributor

@JStickler JStickler commented Jan 21, 2026

What this PR does / why we need it:

Updates the Helm Chart version in the upgrade guide to match the correct version of the charts that this feature was released in, see this comment. The PR that merged this content was created a couple of months ago, and the chart version in his Upgrade update wasn't updated to match the actual Helm version that included his feature.

@JStickler JStickler requested a review from a team as a code owner January 21, 2026 20:18
@JStickler JStickler added type/docs Issues related to technical documentation; the Docs Squad uses this label across many repositories backport release-3.5.x backport release-3.6.x labels Jan 21, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Jan 21, 2026

💻 Deploy preview deleted (docs: fix upgrade Helm version).

@JStickler JStickler merged commit 8d3a79e into main Jan 21, 2026
82 checks passed
@JStickler JStickler deleted the 2026.01.21_Upgrade branch January 21, 2026 21:19
@loki-gh-app
Copy link
Copy Markdown
Contributor

loki-gh-app bot commented Jan 21, 2026

The backport to release-3.5.x 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-20533-to-release-3.5.x origin/release-3.5.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x 8d3a79ef34919954ac1c78089546a7c848ad786c

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-20533-to-release-3.5.x
# Create the PR body template
PR_BODY=$(gh pr view 20533 --json body --template 'Backport 8d3a79ef34919954ac1c78089546a7c848ad786c from #20533{{ "\n\n---\n\n" }}{{ index . "body" }}')
# Create the PR on GitHub
echo "${PR_BODY}" | gh pr create --title 'docs: fix upgrade Helm version (backport release-3.5.x)' --body-file - --label 'size/XS' --label 'type/docs' --label 'backport' --base release-3.5.x --milestone release-3.5.x --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-20533-to-release-3.5.x

# Create a pull request where the `base` branch is `release-3.5.x` and the `compare`/`head` branch is `backport-20533-to-release-3.5.x`.

# Remove the local backport branch
git switch main
git branch -D backport-20533-to-release-3.5.x

@loki-gh-app
Copy link
Copy Markdown
Contributor

loki-gh-app bot commented Jan 21, 2026

The backport to release-3.6.x 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-20533-to-release-3.6.x origin/release-3.6.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x 8d3a79ef34919954ac1c78089546a7c848ad786c

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-20533-to-release-3.6.x
# Create the PR body template
PR_BODY=$(gh pr view 20533 --json body --template 'Backport 8d3a79ef34919954ac1c78089546a7c848ad786c from #20533{{ "\n\n---\n\n" }}{{ index . "body" }}')
# Create the PR on GitHub
echo "${PR_BODY}" | gh pr create --title 'docs: fix upgrade Helm version (backport release-3.6.x)' --body-file - --label 'size/XS' --label 'type/docs' --label 'backport' --base release-3.6.x --milestone release-3.6.x --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-20533-to-release-3.6.x

# Create a pull request where the `base` branch is `release-3.6.x` and the `compare`/`head` branch is `backport-20533-to-release-3.6.x`.

# Remove the local backport branch
git switch main
git branch -D backport-20533-to-release-3.6.x

JStickler added a commit that referenced this pull request Jan 21, 2026
JStickler added a commit that referenced this pull request Jan 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport release-3.5.x backport release-3.6.x backport-failed size/XS type/docs Issues related to technical documentation; the Docs Squad uses this label across many repositories

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants