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
Chore: Bumping go to 1.21.6 #80709
Chore: Bumping go to 1.21.6 #80709
Conversation
* Bumping go to 1.25.6 * bumping sqlite to 1.14.19 * Bumping sqlite version
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-80709-to-v10.0.x origin/v10.0.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x 4083d23f017d5118f80d478d16d52fb65a48b462 When 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-80709-to-v10.0.x
# Create the PR body template
PR_BODY=$(gh pr view 80709 --json body --template 'Backport 4083d23f017d5118f80d478d16d52fb65a48b462 from #80709{{ "\n\n---\n\n" }}{{ index . "body" }}')
# Create the PR on GitHub
echo "${PR_BODY}" | gh pr create --title "[v10.0.x] Chore: Bumping go to 1.21.6" --body-file - --label "type/chore" --label "type/build-packaging" --label "area/backend" --label "dependencies" --label "go" --label "type/ci" --label "no-changelog" --label "backport" --base v10.0.x --milestone 10.0.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-80709-to-v10.0.x
# Create a pull request where the `base` branch is `v10.0.x` and the `compare`/`head` branch is `backport-80709-to-v10.0.x`.
# Remove the local backport branch
git switch main
git branch -D backport-80709-to-v10.0.x |
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-80709-to-v9.5.x origin/v9.5.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x 4083d23f017d5118f80d478d16d52fb65a48b462 When 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-80709-to-v9.5.x
# Create the PR body template
PR_BODY=$(gh pr view 80709 --json body --template 'Backport 4083d23f017d5118f80d478d16d52fb65a48b462 from #80709{{ "\n\n---\n\n" }}{{ index . "body" }}')
# Create the PR on GitHub
echo "${PR_BODY}" | gh pr create --title "[v9.5.x] Chore: Bumping go to 1.21.6" --body-file - --label "type/chore" --label "type/build-packaging" --label "area/backend" --label "dependencies" --label "go" --label "type/ci" --label "no-changelog" --label "backport" --base v9.5.x --milestone 9.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-80709-to-v9.5.x
# Create a pull request where the `base` branch is `v9.5.x` and the `compare`/`head` branch is `backport-80709-to-v9.5.x`.
# Remove the local backport branch
git switch main
git branch -D backport-80709-to-v9.5.x |
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-80709-to-v10.1.x origin/v10.1.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x 4083d23f017d5118f80d478d16d52fb65a48b462 When 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-80709-to-v10.1.x
# Create the PR body template
PR_BODY=$(gh pr view 80709 --json body --template 'Backport 4083d23f017d5118f80d478d16d52fb65a48b462 from #80709{{ "\n\n---\n\n" }}{{ index . "body" }}')
# Create the PR on GitHub
echo "${PR_BODY}" | gh pr create --title "[v10.1.x] Chore: Bumping go to 1.21.6" --body-file - --label "type/chore" --label "type/build-packaging" --label "area/backend" --label "dependencies" --label "go" --label "type/ci" --label "no-changelog" --label "backport" --base v10.1.x --milestone 10.1.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-80709-to-v10.1.x
# Create a pull request where the `base` branch is `v10.1.x` and the `compare`/`head` branch is `backport-80709-to-v10.1.x`.
# Remove the local backport branch
git switch main
git branch -D backport-80709-to-v10.1.x |
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-80709-to-v10.3.x origin/v10.3.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x 4083d23f017d5118f80d478d16d52fb65a48b462 When 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-80709-to-v10.3.x
# Create the PR body template
PR_BODY=$(gh pr view 80709 --json body --template 'Backport 4083d23f017d5118f80d478d16d52fb65a48b462 from #80709{{ "\n\n---\n\n" }}{{ index . "body" }}')
# Create the PR on GitHub
echo "${PR_BODY}" | gh pr create --title "[v10.3.x] Chore: Bumping go to 1.21.6" --body-file - --label "type/chore" --label "type/build-packaging" --label "area/backend" --label "dependencies" --label "go" --label "type/ci" --label "no-changelog" --label "backport" --base v10.3.x --milestone 10.3.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-80709-to-v10.3.x
# Create a pull request where the `base` branch is `v10.3.x` and the `compare`/`head` branch is `backport-80709-to-v10.3.x`.
# Remove the local backport branch
git switch main
git branch -D backport-80709-to-v10.3.x |
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-80709-to-v10.2.x origin/v10.2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x 4083d23f017d5118f80d478d16d52fb65a48b462 When 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-80709-to-v10.2.x
# Create the PR body template
PR_BODY=$(gh pr view 80709 --json body --template 'Backport 4083d23f017d5118f80d478d16d52fb65a48b462 from #80709{{ "\n\n---\n\n" }}{{ index . "body" }}')
# Create the PR on GitHub
echo "${PR_BODY}" | gh pr create --title "[v10.2.x] Chore: Bumping go to 1.21.6" --body-file - --label "type/chore" --label "type/build-packaging" --label "area/backend" --label "dependencies" --label "go" --label "type/ci" --label "no-changelog" --label "backport" --base v10.2.x --milestone 10.2.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-80709-to-v10.2.x
# Create a pull request where the `base` branch is `v10.2.x` and the `compare`/`head` branch is `backport-80709-to-v10.2.x`.
# Remove the local backport branch
git switch main
git branch -D backport-80709-to-v10.2.x |
* Bumping go to 1.25.6 * bumping sqlite to 1.14.19 * Bumping sqlite version (cherry picked from commit 4083d23) # Conflicts: # .drone.yml # .github/workflows/alerting-swagger-gen.yml # .github/workflows/publish-kinds-next.yml # .github/workflows/publish-kinds-release.yml # .github/workflows/verify-kinds.yml # go.mod # go.sum # scripts/drone/variables.star
* Bumping go to 1.25.6 * bumping sqlite to 1.14.19 * Bumping sqlite version (cherry picked from commit 4083d23) # Conflicts: # .drone.yml # .github/workflows/alerting-swagger-gen.yml # .github/workflows/publish-kinds-next.yml # .github/workflows/publish-kinds-release.yml # .github/workflows/verify-kinds.yml # go.mod # go.sum # scripts/drone/variables.star
* Bumping go to 1.25.6 * bumping sqlite to 1.14.19 * Bumping sqlite version (cherry picked from commit 4083d23) # Conflicts: # .drone.yml # scripts/drone/variables.star
* Bumping go to 1.25.6 * bumping sqlite to 1.14.19 * Bumping sqlite version (cherry picked from commit 4083d23) # Conflicts: # .drone.yml # scripts/drone/variables.star
* Bumping go to 1.25.6 * bumping sqlite to 1.14.19 * Bumping sqlite version (cherry picked from commit 4083d23) # Conflicts: # .drone.yml # scripts/drone/variables.star
Chore: Bumping go to 1.21.6 (#80709) * Bumping go to 1.25.6 * bumping sqlite to 1.14.19 * Bumping sqlite version (cherry picked from commit 4083d23) # Conflicts: # .drone.yml # .github/workflows/alerting-swagger-gen.yml # .github/workflows/publish-kinds-next.yml # .github/workflows/publish-kinds-release.yml # .github/workflows/verify-kinds.yml # go.mod # go.sum # scripts/drone/variables.star Co-authored-by: Timur Olzhabayev <timur.olzhabayev@grafana.com>
Chore: Bumping go to 1.21.6 (#80709) * Bumping go to 1.25.6 * bumping sqlite to 1.14.19 * Bumping sqlite version (cherry picked from commit 4083d23) # Conflicts: # .drone.yml # .github/workflows/alerting-swagger-gen.yml # .github/workflows/publish-kinds-next.yml # .github/workflows/publish-kinds-release.yml # .github/workflows/verify-kinds.yml # go.mod # go.sum # scripts/drone/variables.star Co-authored-by: Timur Olzhabayev <timur.olzhabayev@grafana.com>
What is this feature?
Bumping go to 1.21.6 and unpinning the alpine version used as it seems like the bug was resolved in sqlite 1.14.19 mattn/go-sqlite3#1177 (comment)
Why do we need this feature?
Maintenance
Please check that: