Skip to content

ci: test against stable Go 1.27 instead of the release candidate - #25

Merged
mwaldheim merged 1 commit into
mainfrom
ci/go-1.27-stable
Sep 13, 2026
Merged

ci: test against stable Go 1.27 instead of the release candidate#25
mwaldheim merged 1 commit into
mainfrom
ci/go-1.27-stable

Conversation

@mwaldheim

Copy link
Copy Markdown
Contributor

What

Replace the 1.27rc1 CI matrix entry with the stable 1.27 release line.

Why

Go 1.27.0 became generally available in August 2026 and is now at 1.27.1.
Testing against the old release-candidate build no longer adds value once
the final release has shipped. Using 1.27 resolves (via the existing
go-version fallback expression) to the latest 1.27.x patch, and drops the
continue-on-error/lint-skip special-casing that only applied to the
now-obsolete RC build.

This mirrors the same change already present in the main semrel repo CI
matrix.

No Go 1.28 pre-release exists yet to test against — its development cycle
started in July 2026 and RC1 is not expected before around January 2027.

Co-authored-by: Copilot 223556219+Copilot@users.noreply.github.com

…o 1.27.0 has been generally available since August 2026 (now at\n1.27.1). Replace the temporary 1.27rc1 matrix entry with the stable\n1.27 line so CI resolves and tests against the latest 1.27.x patch\nrelease, matching the same treatment already applied in the main\nsemrel repository CI matrix.\n\nNo Go 1.28 pre-release exists yet to add (dev cycle started July\n2026, RC1 not expected before around January 2027).\n\nCo-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@mwaldheim
mwaldheim merged commit 8d77b3d into main Sep 13, 2026
5 checks passed
@mwaldheim
mwaldheim deleted the ci/go-1.27-stable branch September 13, 2026 14:14
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.

1 participant