Update swift-build action to stable version 1.5.0

[leogdion]

No description provided.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

• 🔍 Trigger a full review

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch swift-build-1.5.0

---

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 17.94%. Comparing base (88f1e02) to head (c0d5ad6).
⚠️ Report is 22 commits behind head on v1.0.0-alpha.4.

Additional details and impacted files

@@                Coverage Diff                 @@
##           v1.0.0-alpha.4     #238      +/-   ##
==================================================
+ Coverage           14.27%   17.94%   +3.66%     
==================================================
  Files                  67       78      +11     
  Lines                7179     7829     +650     
==================================================
+ Hits                 1025     1405     +380     
- Misses               6154     6424     +270     

Flag	Coverage Δ
spm	17.88% <ø> (+3.60%)	⬆️
swift-6.1-jammy	17.89% <ø> (+3.61%)	⬆️
swift-6.1-noble	17.92% <ø> (+3.64%)	⬆️
swift-6.2-jammy	17.88% <ø> (+3.60%)	⬆️
swift-6.2-jammynightly	?
swift-6.2-noble	17.89% <ø> (+3.61%)	⬆️
swift-6.2-noblenightly	?
swift-6.3-jammynightly	17.88% <ø> (?)
swift-6.3-noblenightly	17.88% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[claude]

Pull Request Review: Update swift-build action to stable version 1.5.0

Summary

This PR updates the brightdigit/swift-build GitHub Action from v1.5.0-beta.2 to the stable 1.5.0 release across all workflow jobs.

Code Quality ✅

Strengths:

• Clean, consistent change across all 4 workflow jobs (Ubuntu, Windows, Android, macOS)
• Proper semantic versioning upgrade from beta to stable release
• No breaking changes in the action interface - all parameters remain compatible

Observations:

• The version format changes from v1.5.0-beta.2 (with v prefix) to 1.5.0 (without prefix)
• Both formats are valid for GitHub Actions, but the new format aligns with the action's current tagging convention

Testing Considerations ⚠️

Recommendation: Verify the following before merging:

1. Build Matrix Coverage: This change affects multiple build configurations:

   • Ubuntu (Swift 6.1, 6.2, 6.3 across noble/jammy with standard/WASM builds)
   • Windows (2022/2025 runners with Swift 6.1/6.2)
   • Android (API levels 33/34 with Swift 6.1/6.2)
   • macOS (Xcode 16.3, 16.4, 26.2 with iOS/watchOS/tvOS/visionOS simulators)

2. Critical Test Points:

   • WASM builds with custom Swift flags (lines 42-46)
   • Code coverage collection and Codecov uploads
   • Android test execution (android-run-tests: true)
   • Platform simulator downloads for Apple platforms

3. CI Validation: Ensure all jobs complete successfully, particularly:

   • Coverage output parsing (steps.build.outputs.contains-code-coverage)
   • Windows-specific coverage handling (using codecov-action@v5 vs v4)

Potential Issues 🔍

None identified, but monitor for:

• Any behavioral changes in the stable release vs beta (check action release notes)
• Coverage file generation consistency across platforms
• WASM build compatibility with wasmtime 40.0.2

Security ✅

No security concerns:

• GitHub Actions version pins are maintained
• No credential exposure or permission changes
• Uses standard action versioning practices

Performance ✅

Expected impact: Neutral to positive

• Stable releases typically include performance optimizations
• No workflow logic changes that would affect CI runtime

Best Practices ✅

The PR follows MistKit conventions:

• Consistent version updates across all jobs
• Maintains platform-specific configurations
• Preserves existing test coverage infrastructure

Recommendations

1. Before merging: Run full CI suite to validate all build configurations
2. Consider: Add a comment in the PR body linking to swift-build 1.5.0 release notes if available
3. Future: Consider setting up Dependabot to automate action updates

Verdict: ✅ APPROVE with CI validation

This is a low-risk upgrade that moves from a beta to a stable release. The changes are mechanical and consistent. Recommend merging after CI passes successfully across all platforms.

---

Review conducted by Claude Code following MistKit project guidelines

[claude]

Pull Request Review: Update swift-build action to stable version 1.5.0

Summary

This PR updates the brightdigit/swift-build action from version v1.5.0-beta.2 to the stable release 1.5.0 across all CI workflows.

✅ Code Quality & Best Practices

Excellent:

• Clean, focused change with a single clear purpose
• Consistent update across all 4 occurrences in the workflow file
• Following semantic versioning best practice by moving from beta to stable release
• No breaking changes expected (minor version update within v1.5.x)

✅ Correctness

All occurrences updated:

1. Line 37: Ubuntu builds (standard, WASM, WASM-embedded)
2. Line 76: Windows builds (2022 & 2025)
3. Line 116: Android builds
4. Line 193: macOS builds (including iOS, watchOS, tvOS, visionOS)

No issues found - the change is straightforward and correct.

✅ Performance Considerations

Positive impact expected:

• Stable releases typically include performance optimizations and bug fixes from beta period
• No performance regressions expected from a stable release
• CI reliability should improve with stable release vs beta

✅ Security Concerns

Low risk:

• GitHub Actions version pinning is appropriate (not using @main or @latest)
• Moving from beta to stable generally improves security posture
• Action is from trusted source (brightdigit organization)

Recommendation: Consider using the full SHA-256 commit hash for maximum security (e.g., brightdigit/swift-build@<commit-sha>) in the future, though version tags are acceptable for most use cases.

⚠️ Test Coverage

Observation:
The PR modifies CI workflow configuration but doesn't include:

• Updates to documentation mentioning the action version
• Changelog entry documenting the upgrade

Low priority since this is infrastructure, but consider documenting dependency updates.

🔍 Additional Observations

1. Consistency check passed: All 4 instances of the action reference are updated
2. Matrix coverage: Update applies to all platform builds (Ubuntu, Windows, Android, macOS/iOS/watchOS/tvOS/visionOS)
3. No parameter changes needed: The action interface appears stable between beta.2 and 1.5.0

📋 Recommendations

Before merging:

1. ✅ Ready to merge from a code perspective
2. 📝 Consider adding a note to CHANGELOG.md under "Infrastructure" or "CI" section
3. 🧪 Monitor the first CI run with the stable version to ensure no unexpected behavior

Optional improvements:

• Add a comment in the workflow file noting the action version (e.g., # Using swift-build@1.5.0 (stable))
• Document the version requirement in CONTRIBUTING.md if developer setup instructions exist

✨ Verdict

APPROVED ✓

This is a clean, low-risk infrastructure update that moves from beta to stable release. The change is:

• ✅ Correctly implemented
• ✅ Consistently applied
• ✅ Following best practices
• ✅ No security concerns
• ✅ Expected to improve CI reliability

Feel free to merge once CI passes successfully with the new stable version!