[CHORE] Parallelize release tests and clarify CI job names#255
Merged
Conversation
- Parallelize createRelease test job by platform via a matrix, matching unitTests.yml - Switch unitTests.yml matrix from a nested `env` object to scalar `xcode` and `platform` keys so the Xcode version stays in the job name when invoked as a reusable workflow from integrationTests.yml - Give integrationTests.yml jobs the same `Xcode_X.Y / platform` naming - Extract Xcode select + simulator-name resolution into `.github/actions/setup-xcode` composite action so version→simulator mappings live in one place - Hoist Xcode version in createRelease.yml into a workflow-level `XCODE_VERSION` env so it can be bumped in a single spot Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
`env` context isn't available in `jobs.<job_id>.name`, so the previous
`${{ env.XCODE_VERSION }}` reference there failed to parse. Use a static
`Test / <platform>` job name and keep `${{ env.XCODE_VERSION }}` in
step-level fields where it is supported.
Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
calvinbayer
approved these changes
May 15, 2026
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
2 participants
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.
Summary
unitTests.yml.unitTests.ymlandintegrationTests.ymlnow showXcode_X.Y / platform, including whenunitTests.ymlis called as a reusable workflow fromintegrationTests.yml(previously the Xcode version was dropped because the matrix used a nestedenvobject — switched to scalarxcode/platformkeys)..github/actions/setup-xcodecomposite action that selects an Xcode version and emits the matching simulator names as outputs, so the version→simulator mapping lives in a single file instead of being duplicated across each workflow.createRelease.ymlhoists the Xcode version into a workflow-levelXCODE_VERSIONenv var so it can be bumped once.Test plan
Xcode_26.X / <platform>in checks.Integration Testsand confirm theunit / Xcode_26.X / <platform>andintegration / Xcode_26.X / <platform>jobs show the Xcode version in their names.Create new releaseagainst a throwaway version and confirm thetestjob fans out into five platform-specific jobs.Xcode_99.0).🤖 Generated with Claude Code