chore: Release PR checks no longer fail on an environment-dependent unit test

[hatayama]

Summary

• Fixes the build-cli failure that reappeared on the regenerated release PR (chore: release v3-beta #1278) after chore: Unblock the v3-beta release: align the next CLI release with the stamped version and stop release PRs failing the CLI version check #1325.

User Impact

• Before: TestMinimumVersionWarningSkipsMissingBaseRefBeforeRepositoryResolution failed when the test suite ran on the release PR's own CI, keeping the release blocked.
• After: the test passes regardless of the CI environment, so the release PR can go green.

Changes

• GitHub Actions sets GITHUB_HEAD_REF for every step of pull_request runs. On the release PR that value is release-please--branches--v3-beta, so the release-please skip introduced in chore: Unblock the v3-beta release: align the next CLI release with the stamped version and stop release PRs failing the CLI version check #1325 fired before the base-ref skip the test asserts. The test now clears GITHUB_HEAD_REF explicitly, the same way the architecture test harness already controls it.

Verification

• GITHUB_HEAD_REF=release-please--branches--v3-beta GITHUB_BASE_REF=v3-beta go test ./... -count=1 reproduced the CI failure before the fix and passes after it
• scripts/check-go-cli.sh: all green

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 39bb3182-a0df-43a0-a042-8d9462025982

📥 Commits

Reviewing files that changed from the base of the PR and between d5ae563 and a95f228.

📒 Files selected for processing (1)

• cli/internal/automation/minimum_version_warning_test.go

---

📝 Walkthrough

Walkthrough

Test TestMinimumVersionWarningSkipsMissingBaseRefBeforeRepositoryResolution now explicitly clears GITHUB_HEAD_REF environment variable to ensure the missing base ref skip behavior is evaluated before dependent logic runs.

Changes

Test environment fix

Layer / File(s)	Summary
Environment variable cleanup in version warning test cli/internal/automation/minimum_version_warning_test.go	Test adds t.Setenv("GITHUB_HEAD_REF", "") to clear CI's PR head branch so the base-ref skip is the first condition evaluated.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• hatayama/unity-cli-loop#1244: Both PRs modify the CLI minimum-version warning test suite in minimum_version_warning_test.go, directly connected to the same test logic for missing-base-ref handling.

• hatayama/unity-cli-loop#1246: This test change (clearing GITHUB_HEAD_REF to force the missing base ref skip path) is directly related to updates in RunMinimumVersionWarning that depend on PR head/base ref handling.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: fixing a unit test that was failing in certain CI environments due to environment-dependent behavior.
Description check	✅ Passed	The description is comprehensive and directly related to the changeset, explaining the problem, root cause, solution, and verification steps for the test fix.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
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 docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/clear-head-ref-in-minimum-version-unit-test

---

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.}

[cubic-dev-ai]

No issues found across 1 file

_{Re-trigger cubic}