Skip to content

ci: bump Go matrix to 1.23/stable (macOS Sequoia LC_UUID fix)#10

Merged
github-actions[bot] merged 1 commit into
mainfrom
dev
Jul 4, 2026
Merged

ci: bump Go matrix to 1.23/stable (macOS Sequoia LC_UUID fix)#10
github-actions[bot] merged 1 commit into
mainfrom
dev

Conversation

@mar0ls

@mar0ls mar0ls commented Jul 4, 2026

Copy link
Copy Markdown
Owner

Summary

  • Bump Go CI matrix from '1.22, stable' to '1.23, stable'.
  • Go 1.22 aborts on macOS Sequoia+ runners with 'dyld: missing LC_UUID' (crypto/tls: add GetEncryptedClientHelloKeys callback golang/go#71920, fixed in 1.23.4, no 1.22 backport).
  • Only the macos-latest + 1.22 slot fails on v0.5.0 — 5/6 slots pass. Code is fine; toolchain is not.
  • go.mod still declares 'go 1.22' — consumers on 1.22 remain supported, CI just doesn't verify it.
  • Document the automerge / required-checks interaction so future PRs are not merged with red CI.

Test plan

  • All 6 matrix slots green (3 OS × [1.23, stable]) after this merges to dev.
  • Enable required status checks on main in Settings → Branches so --auto no longer degrades to instant merge.

Follow-ups (outside this PR)

  • Tag v0.5.1 (CI-only, no code changes) so the release page shows a green build.
  • Push to main is expected not to re-trigger CI because auto-merge uses GITHUB_TOKEN (documented GitHub behavior). Re-triggering after tag push is one option.

Go 1.22 hits a dyld 'missing LC_UUID' linker bug on macOS Sequoia+ runners
(golang/go#71920, fixed in 1.23.4). The bug is toolchain-side, not code:
5/6 matrix slots pass on v0.5.0, only macos-latest+1.22 aborts before any
test runs. Bumping the CI matrix to 1.23 and stable removes the failing
slot. go.mod still declares 'go 1.22' so consumers on 1.22 can use the
library — CI only tests what it can build.

Also document why the --auto flag in automerge.yml merged v0.5 despite the
CI failure: without required status checks configured under main's branch
protection, --auto degrades to an immediate merge. Enabling required
checks in Settings -> Branches is the fix; this is a repo-config step, not
a workflow change.
Copilot AI review requested due to automatic review settings July 4, 2026 12:16
@github-actions github-actions Bot enabled auto-merge July 4, 2026 12:16
@github-actions github-actions Bot merged commit 90739d6 into main Jul 4, 2026
26 checks passed
@codecov

codecov Bot commented Jul 4, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates CI configuration to avoid a known Go 1.22 toolchain failure on macOS Sequoia+ GitHub runners, while documenting why --auto merges may not be gated by CI unless branch protection “required checks” are configured.

Changes:

  • Bump the Go test matrix from 1.22 to 1.23 (keeping stable) to avoid the macOS Sequoia dyld: missing LC_UUID failure.
  • Add inline documentation clarifying that go.mod still targets Go 1.22 (consumer support unchanged) even though CI no longer exercises 1.22.
  • Document the GitHub auto-merge vs. required-checks interaction in the automerge workflow.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
.github/workflows/test.yml Updates the Go version matrix to 1.23/stable and documents the macOS runner/toolchain issue.
.github/workflows/automerge.yml Adds workflow-level documentation about required status checks needed for --auto to actually defer merges.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

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.

2 participants