Repository navigation
ci: tag releases for Swift Package Manager - #9
Merged
lemarier merged 1 commit intoSep 24, 2026
Merged
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configurationConfiguration used: Organization UI Review profile: QUIET Plan: Advanced Run ID: 📒 Files selected for processing (3)
Comment |
lemarier
deleted the
lemarier/publish-a-swift-compatible-ui-package-version
branch
September 24, 2026 12:39
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
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.
Swift Package Manager only resolves semantic-version tags, and this repository only had
@origin89/ui-react@<version>tags, so the README's0.1.0Swift requirement could not resolve. After a successful npm publish,publish-react.ymlnow adds a lightweight<version>tag (for example0.2.0) at the released commit. That commit has already passed the Swift, iOS Simulator and Android jobs. The job fails instead of moving an existing tag that points elsewhere. The Swift version follows the React package version.The README now points Swift consumers at an exact version and React consumers at npm; it also drops the
v0.1.0GitHub release reference, since that release does not exist. The existing0.2.0release ateeae8acgot a one-time backfilled0.2.0tag, pushed separately; a clean package depending onexact: "0.2.0"resolves that revision and builds on macOS. The inaccurate Android release-asset claim is tracked in #8.Validation:
biome ci .passes; the workflow YAML parses;gh api .../git/ref/tags/0.2.0returned 404 and exited non-zero before the backfill, so the job takes the create branch. The new job has not run in Actions yet.Closes #7