ci: stop pinning Xcode 16.2 in the publish workflow - #22
Merged
Conversation
macOS-latest no longer ships Xcode 16.2 — the runner now offers 26.0 through 26.6 — so "Select Xcode 16.2" fails outright and the 0.5.0 publish never reached Gradle. build.yml already asks for latest-stable and passes on the same runner; publish.yml now matches it. The failure was clean: it happened three steps in, before any Gradle work, so nothing was uploaded.
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.
The 0.5.0 publish failed. Not the library — the runner:
macOS-latestno longer ships Xcode 16.2, soSelect Xcode 16.2fails outright. It failed three steps in, before any Gradle work, so nothing was uploaded to Maven Central — the release is tagged and published on GitHub, but the artifacts are not out.build.ymlalready asks forlatest-stableand passed on the same runner minutes earlier (bothTest All PlatformsandBuild Library), so this alignspublish.ymlwith the workflow that is known good.Workflow-only change; no source touched.