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

golang: bump Go version to 1.22.9-1 #11010

Conversation

microsoft-golang-bot
Copy link
Contributor

@microsoft-golang-bot microsoft-golang-bot commented Nov 11, 2024

Hi! 👋 I'm the Microsoft Go team's bot. This is an automated pull request I generated to bump the Go version to 1.22.9-1.

I'm not able to run the Azure Linux pipelines yet, so the Microsoft Go release runner will need to finalize this PR. @dagood

Finalization steps:

  • Trigger Source Tarball Publishing with:
    Full Name:
    go1.22.9-20241107.6.src.tar.gz
    
    URL:
    https://github.com/microsoft/go/releases/download/v1.22.9-1/go1.22.9-20241107.6.src.tar.gz
    
  • Trigger the Buddy Build with:
    First field:
    PR-11010
    
    Core spec:
    golang
    
  • Post a PR comment with the URL of the triggered Buddy Build.
  • Mark this draft PR as ready for review.

Thanks!

@dagood
Copy link
Member

dagood commented Nov 11, 2024

I'm not sure what to put in the buddy build as the core spec (package name, or spec file filename?) so I did both for now:
golang: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=673668&view=results
golang-1.22: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=673669&view=results

(Edit: It looks like golang-1.22 is the right one.)

@dagood dagood marked this pull request as ready for review November 11, 2024 22:29
@dagood dagood requested a review from a team as a code owner November 11, 2024 22:29
@dagood
Copy link
Member

dagood commented Dec 2, 2024

cgmanifest.json conflict. My quick automation fix for the spec file split probably isn't enough and we should have a way to generate both updates in the same PR to avoid a conflict/respin/etc.

@dagood dagood closed this Dec 2, 2024
@dagood
Copy link
Member

dagood commented Dec 2, 2024

The conflict is actually just a side effect of the issue fixed by #11286 and shouldn't happen in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants