test if go is available on macos 26

[suzuki-shunsuke]

Summary by CodeRabbit

• Chores
  • Updated CI/CD testing infrastructure to run tests across multiple architectures (amd64 and arm64) for improved compatibility verification.

[coderabbitai]

📝 Walkthrough

Walkthrough

The test workflow trigger was simplified from conditional pull_request and pull_request_review events to a single pull_request trigger. Job configuration changed from one Ubuntu runner to two macOS runners for architecture-specific testing. Permissions were reduced and the notification step was removed.

Changes

Workflow Trigger and Job Architecture

Layer / File(s)	Summary
Workflow trigger, job architecture, and step simplification .github/workflows/test.yaml	Workflow trigger simplified from multiple event types with conditional logic to single pull_request trigger. Single Ubuntu-based job replaced with two parallel macOS jobs (test-amd64, test-arm64) for different architectures. Job permissions reduced from explicit pull-requests: write and contents: read to empty object. Notification action step removed and replaced with go version check.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 Our workflows hop in parallel now,
Two macOS runners take a bow!
The triggers simplified, clean and bright,
Architectures tested, left and right!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The pull request title clearly and specifically describes the main change: testing Go availability on macOS 26 runners, which aligns with the workflow restructuring from Ubuntu to macOS runners.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch test-macos-26-go

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

🧹 Nitpick comments (2)

.github/workflows/test.yaml (2)

17-17: ⚡ Quick win

Consider adding diagnostic output for more informative test results.

Same suggestion as for test-amd64: adding system diagnostics would make this test more informative.

💡 Optional enhancement to add diagnostic information

     steps:
-      - run: go version
+      - name: Check Go availability and system info
+        run: |
+          echo "Go version:"
+          go version
+          echo "Architecture:"
+          uname -m
+          echo "macOS version:"
+          sw_vers

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/test.yaml at line 17, The workflow currently only runs
"run: go version"; expand this diagnostic step to emit more system and Go
environment details for the test job (the step that currently contains "run: go
version") by adding commands that print kernel/os info (e.g. uname -a or
/etc/os-release), distribution details, disk and memory stats (df -h, free -h),
and Go environment details (go env) so test failures include useful environment
context; update the same step (the one with "run: go version") to run those
commands in sequence and ensure output is shown in the job logs.

---

10-10: ⚡ Quick win

Consider adding diagnostic output for more informative test results.

While go version checks if Go is available, you could make this test more informative by adding system details.

💡 Optional enhancement to add diagnostic information

     steps:
-      - run: go version
+      - name: Check Go availability and system info
+        run: |
+          echo "Go version:"
+          go version
+          echo "Architecture:"
+          uname -m
+          echo "macOS version:"
+          sw_vers

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/test.yaml at line 10, Replace or augment the existing
"run: go version" step to emit additional diagnostics so CI failures are easier
to debug: keep the "go version" call and add commands to print OS/kernel info
(e.g., uname -a), Go environment details (go env), and workspace contents (e.g.,
ls -la) — target the same workflow step that currently contains "run: go
version" so the added diagnostics run in the same job context and provide more
informative test output.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In @.github/workflows/test.yaml:
- Line 17: The workflow currently only runs "run: go version"; expand this
diagnostic step to emit more system and Go environment details for the test job
(the step that currently contains "run: go version") by adding commands that
print kernel/os info (e.g. uname -a or /etc/os-release), distribution details,
disk and memory stats (df -h, free -h), and Go environment details (go env) so
test failures include useful environment context; update the same step (the one
with "run: go version") to run those commands in sequence and ensure output is
shown in the job logs.
- Line 10: Replace or augment the existing "run: go version" step to emit
additional diagnostics so CI failures are easier to debug: keep the "go version"
call and add commands to print OS/kernel info (e.g., uname -a), Go environment
details (go env), and workspace contents (e.g., ls -la) — target the same
workflow step that currently contains "run: go version" so the added diagnostics
run in the same job context and provide more informative test output.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 5e188337-0dec-4d94-b50a-4f2f54e35082

📥 Commits

Reviewing files that changed from the base of the PR and between 0e685d9 and e189bfe.

📒 Files selected for processing (1)

• .github/workflows/test.yaml