Skip to content

Adding VersionStream for go-1.26#78619

Closed
octo-sts[bot] wants to merge 2 commits intomainfrom
go-1.26
Closed

Adding VersionStream for go-1.26#78619
octo-sts[bot] wants to merge 2 commits intomainfrom
go-1.26

Conversation

@octo-sts
Copy link
Contributor

@octo-sts octo-sts bot commented Feb 12, 2026

No description provided.

@tiborvass
Copy link

How to resolve the issues with upgrading to go 1.26 ?

@sergiodj
Copy link
Member

How to resolve the issues with upgrading to go 1.26 ?

Hi @tiborvass , what kind of issues are you experiencing? Could you please open a separate issue for them? This PR will be closed as Go 1.26 is already present in the archive. Thanks!

@sergiodj sergiodj closed this Feb 23, 2026
@tiborvass
Copy link

tiborvass commented Feb 24, 2026

@xnox @sergiodj

Codex found what is missing, though I'm not sure what these p:go= lines mean.

- https://packages.wolfi.dev/os/aarch64/APKINDEX.tar.gz

  In that file, the go~... constraint is matched against p:go=... lines. The highest p:go= currently is 1.25.7-r0, which is why the solver reported
  1.25.7 as latest satisfier.

  Relevant check:

  curl -fsSL https://packages.wolfi.dev/os/aarch64/APKINDEX.tar.gz \
  | tar -xzO APKINDEX \
  | grep '^p:go=' \
  | sed 's/^p:go=//' \
  | sort -V | tail -n 5

  (There is a P:go-1.26 entry, but it currently has no p:go=1.26... provide line.)

@tiborvass
Copy link

@tiborvass
Copy link

Opened issue #78640

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants