golang: bump Go version to 1.25.0-1; major version update

[dagood]

• Based on golang: bump Go version to 1.25.0-1 #14510
  • Bump the Go version to 1.25.0-1.
• Update Go major versions maintained in Azure Linux by putting 1.24 into versioned golang-1.24.spec, adding 1.25, and deleting 1.23.
• Buddy build for golang golang-1.24 core specs: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=898561&view=results

Important

This release adds toolchain telemetry.

[CBL-Mariner-Bot]

✅ PR Check Passed

No critical issues detected in spec file changes.

🤖 AI Analysis Summary:

Brief Analysis: The spec file updates largely adjust BuildRequires to “golang < 1.25” and increment release numbers, while ensuring CVE patches remain referenced and applied via %autopatch.
Critical Issues Found: No ERROR/CRITICAL issues were detected—the referenced CVE patch files are present and properly named, and the changelog entries document CVE fixes with the correct upstream attribution.
Recommended Actions:
• Verify that all other spec files maintain sequential patch numbering and proper %autopatch usage.
• Confirm that historical changelog entries match the applied patches for context consistency.
• Continue monitoring version updates for future security implications.

---

📋 For detailed analysis and recommendations, check the Azure DevOps pipeline logs.

[mfrw]

NACK -
I feel we should at least get some clarity on what is our steps forward with a few specs that I have a slight concern with.

[mfrw]

I am taking a look the specs and I have a concern w.r.t a few packages (this is something that caught my eye today):

• libguestfs
• libnvidia-container
• gh
• nvidia-container-toolkit
• moby-containerd-cc
• vitess

[anphel31]

Thanks for checking this - I believe these packages will need to be patched/updated to be compatible with 1.24/1.25 before we remove the 1.23 spec.

[mfrw]

Thank you Andrew :)

[dagood]

As an experiment, Here's a buddy build that includes the old 1.23: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=906521&view=results

[mfrw]

Changes look good to me :)
Requesting @anphel31 to take a look as well :)

Thank you @dagood.

[anphel31]

I ran a full build with this change: 3.0.20250829-anphel-912722
x64 BuildRPMS
Arm64 BuildRpms
With these changes, a number of packages are now building with go 1.25, and hitting some build failures.
The most common error I see is Using a crypto backend requires CGO_ENABLED=1.
List of failing arm64 packages:

Failed SRPMs:
-->cf-cli-8.7.11-3.azl3.src.rpm
-->cloud-provider-kubevirt-0.5.1-1.azl3.src.rpm
-->containerd2-2.0.0-13.azl3.src.rpm
-->containerized-data-importer-1.57.0-14.azl3.src.rpm
-->coredns-1.11.4-7.azl3.src.rpm
-->cri-tools-1.32.0-2.azl3.src.rpm
-->dcos-cli-1.2.0-18.azl3.src.rpm
-->docker-buildx-0.14.0-6.azl3.src.rpm
-->flannel-0.24.2-15.azl3.src.rpm
-->jx-3.10.182-1.azl3.src.rpm
-->kubernetes-1.30.10-9.azl3.src.rpm
-->multus-4.0.2-5.azl3.src.rpm
-->prometheus-adapter-0.12.0-3.azl3.src.rpm
-->prometheus-process-exporter-0.8.2-2.azl3.src.rpm

Looks like more details here: https://devblogs.microsoft.com/go/microsoft-go-defaults-to-system-crypto/

[anphel31]

Blocking for now due to the package breaks in the full build (see my previous comment).
I'm fine with upgrading to go 1.25 and keeping the 1.23 spec around temporarily, but we will need to sort out the build breaks before merging.

[anphel31]

My changes to resolve the build breaks by pinning incompatible packages to golang 1.24 are visible here: https://github.com/microsoft/azurelinux/compare/3.0-dev...anphel/clone-dev/dagood/go-1.25?expand=1
@dagood could you integrate these changes into your branch?

[Kanishk-Bansal]

/azurepipelines run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[dagood]

Thanks, applied fixes. New buddy build: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=918100&view=results

[Kanishk-Bansal]

@dagood, could you please retarget your branch to fasttrack/3.0 ? We need to ship the rpm as soon as possible.

[dagood]

@dagood, could you please retarget your branch to fasttrack/3.0 ? We need to ship the rpm as soon as possible.

It seems like there are a lot of conflicts if I try to rebase (8 files). I'm not sure how that branch is meant to operate. It seems to me like it would be better/faster if an Azure Linux maintainer does this.

[dagood]

Here's my attempt at a fasttrack/3.0 port: #14616

[dagood]

• Closing in favor of golang: bump Go version; major version update [fasttrack/3.0] #14616