ci: run tests on every PR and gate releases on the test suite - #9
Merged
Merged
Conversation
Adds a CI workflow (swift build + swift test on macOS) and a test step to the release job, so a regression can no longer ship straight from a developer machine into a signed, auto-delivered release. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Addresses the medium-severity audit finding that no automated tests ran anywhere in CI:
ci.ymlworkflow:swift build+swift test(47 tests, ~1 min) on every PR and push tomain, using the same Xcode-selection logic as the release workflow.swift testbefore building, so a tagged release can't ship with a failing suite.🤖 Generated with Claude Code