Skip to content
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

Bump go to v1.22.7 #4979

Merged
merged 1 commit into from
Sep 17, 2024
Merged

Bump go to v1.22.7 #4979

merged 1 commit into from
Sep 17, 2024

Conversation

ncopa
Copy link
Collaborator

@ncopa ncopa commented Sep 16, 2024

https://groups.google.com/g/golang-announce/c/K-cEzDeCtpc?pli=1 https://go.dev/doc/devel/release#go1.22.7
https://github.com/golang/go/issues?q=milestone%3AGo1.22.7+label%3ACherryPickApproved

Description

Fixes # (issue)

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update

How Has This Been Tested?

  • Manual test
  • Auto test added

Checklist:

  • My code follows the style guidelines of this project
  • My commit messages are signed-off
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules
  • I have checked my code and corrected any misspellings

@ncopa ncopa requested a review from a team as a code owner September 16, 2024 12:29
@ncopa ncopa added chore backport/release-1.29 PR that needs to be backported/cherrypicked to the release-1.29 branch backport/release-1.30 PR that needs to be backported/cherrypicked to the release-1.30 branch labels Sep 16, 2024
@twz123 twz123 added the backport/release-1.28 PR that needs to be backported/cherrypicked to release-1.28 branch label Sep 17, 2024
@twz123 twz123 merged commit c96cce3 into k0sproject:main Sep 17, 2024
90 checks passed
@k0s-bot
Copy link

k0s-bot commented Sep 17, 2024

Backport failed for release-1.28, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin release-1.28
git worktree add -d .worktree/backport-4979-to-release-1.28 origin/release-1.28
cd .worktree/backport-4979-to-release-1.28
git switch --create backport-4979-to-release-1.28
git cherry-pick -x 293a3c233ccd5310715ba3a86de924c4a3251c04

@k0s-bot
Copy link

k0s-bot commented Sep 17, 2024

Successfully created backport PR for release-1.29:

@k0s-bot
Copy link

k0s-bot commented Sep 17, 2024

Successfully created backport PR for release-1.30:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport/release-1.28 PR that needs to be backported/cherrypicked to release-1.28 branch backport/release-1.29 PR that needs to be backported/cherrypicked to the release-1.29 branch backport/release-1.30 PR that needs to be backported/cherrypicked to the release-1.30 branch chore
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants