fix: upgrade Go snap to 1.26 in snapcraft.yaml#2011
Merged
TerryHowe merged 1 commit intooras-project:release-1.3from Mar 20, 2026
Merged
fix: upgrade Go snap to 1.26 in snapcraft.yaml#2011TerryHowe merged 1 commit intooras-project:release-1.3from
TerryHowe merged 1 commit intooras-project:release-1.3from
Conversation
The go.mod requires Go 1.26.1, but the build snap was pinned to
go/1.25/stable. When Go 1.25 encounters a go.mod with a higher
version requirement, it attempts to auto-download that version via
GOTOOLCHAIN. Snapcraft's environment validator then receives the
download progress string ('go: downloading go1.26.1 (linux/amd64)')
as the Go compiler version, which is invalid, causing the snap build
to fail.
Upgrade the build snap channel from go/1.25/stable to go/1.26/stable
to match the Go version required by go.mod.
Signed-off-by: Terry Howe <terrylhowe@gmail.com>
TerryHowe
requested review from
Wwwsylvia,
sabre1041,
sajayantony and
shizhMSFT
as code owners
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## release-1.3 #2011 +/- ##
===============================================
+ Coverage 87.25% 87.28% +0.03%
===============================================
Files 143 143
Lines 5538 5538
===============================================
+ Hits 4832 4834 +2
+ Misses 419 417 -2
Partials 287 287 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
sajayantony
approved these changes
Mar 20, 2026
FeynmanZhou
pushed a commit
to oras-project/oras-www
that referenced
this pull request
Apr 15, 2026
## Summary The snap installation section was removed from the v1.3 docs, which prompted issue oras-project/oras#1965. Now that the snap release workflow is active and publishing to the Snap Store (as of oras-project/oras#2011), restore the installation instructions. ## Changes - Adds a **Snap** section to `versioned_docs/version-1.3/installation.mdx` with `snap install oras --classic` - Includes a note explaining that `--classic` is required because ORAS uses classic confinement to access files outside the snap sandbox - Adds Snap to the list of package managers mentioned in the verification note ## Why `--classic` is required ORAS is a CLI tool that reads and writes files at arbitrary paths provided by the user. Strict snap confinement would prevent this, so classic confinement is intentional and the `--classic` flag is unavoidable. Fixes oras-project/oras#1965 Signed-off-by: Terry Howe <terrylhowe@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The snap release CI job for
release-1.3is failing with:Root Cause
snapcraft.yamlpins the build snap togo/1.25/stable, butgo.modrequiresgo 1.26.1. Go 1.21+ defaults toGOTOOLCHAIN=auto, which causes the Go 1.25 binary to attempt downloading Go 1.26.1 at build time. Snapcraft's environment validator then receives the download progress message (go: downloading go1.26.1 (linux/amd64)) as the Go compiler version string — which is invalid — causing the build to fail.Fix
Upgrade the build snap channel from
go/1.25/stabletogo/1.26/stableto match the Go version required bygo.mod.References