ci: avoid flaky SwiftPM test runner hangs

[D1a0y1bb]

Summary

Stabilize the macOS CI and release validation workflows after repeated GitHub runner hangs in the SwiftPM swift test execution path.

Changes

• Replace the CI swift test step with swift build --build-tests, keeping SwiftPM package/test-target compilation coverage without launching the flaky swiftpm-testing runner.
• Remove the duplicate swift test --parallel lightweight smoke step from CI. The same suite is already covered by the Xcode test step, and the parallel SwiftPM runner was the timeout source.
• Apply the same SwiftPM test-build change to the Release workflow so release dry-runs do not rely on the same unstable SwiftPM runner path.

Validation

• ruby -e 'require "yaml"; YAML.load_file(".github/workflows/ci.yml"); YAML.load_file(".github/workflows/release.yml")'
• git diff --check
• swift build --package-path PitcherPlantApp --build-tests
• xcodebuild -project PitcherPlantApp/PitcherPlantApp.xcodeproj -scheme PitcherPlantApp -destination 'platform=macOS' test — 119 tests passed, TEST SUCCEEDED

Notes

The failing master runs timed out inside swiftpm-testing after many tests had already reported success. Xcode tests completed successfully in the same workflows, so this keeps the real test gate on the stable Xcode test path instead of repeating the suite through SwiftPM.

Summary by CodeRabbit

• Chores
  • Updated continuous integration workflow to build test targets instead of running the full test suite.
  • Removed redundant performance and integration testing step from the CI pipeline.
  • Updated release workflow testing approach to align with CI changes.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 497f1558-69c9-47fd-a44a-7eafc50d4207

📥 Commits

Reviewing files that changed from the base of the PR and between ea71b07 and 8e7b3a4.

📒 Files selected for processing (2)

• .github/workflows/ci.yml
• .github/workflows/release.yml

---

📝 Walkthrough

Walkthrough

GitHub Actions workflows for macOS CI and release jobs are updated to build Swift test targets instead of executing them. The CI workflow replaces swift test with swift build --build-tests and removes a dedicated parallel test step, while the release workflow similarly transitions from test execution to test building.

Changes

Test Execution Strategy

Layer / File(s)	Summary
CI workflow test execution changes .github/workflows/ci.yml	The SwiftPM test phase replaces swift test with swift build --build-tests, and the lightweight integration and performance smoke test step running swift test --parallel is removed.
Release workflow test execution changes .github/workflows/release.yml	The SwiftPM testing step is replaced with a test build step that builds test targets via swift build --build-tests instead of running them.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 Build, don't run, the test commands say,
Swift workflows hop a leaner way.
Less parallel, more compile time,
The CI gardens now align.

🚥 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 title clearly and specifically summarizes the main change: replacing flaky SwiftPM test runner with build-only approach to avoid hangs in CI workflows.
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 PitcherPlant/stabilize-ci-swiftpm-tests

---

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