Skip to content

chore: fix release - #205

Merged
stevensJourney merged 2 commits into
mainfrom
fix-release
Jul 27, 2026
Merged

chore: fix release#205
stevensJourney merged 2 commits into
mainfrom
fix-release

Conversation

@stevensJourney

Copy link
Copy Markdown
Contributor

The iOS publish job is currently failing with:

release not found

When attempting to upload the XCFramework to the draft Github release.

It seems like the iOS workflow does not have the write permission configured. Which is needed to upload files to a release.

AI usage: The fix was found by Codex GPT 5.6

The v0.5.0 draft release currently does not include iOS frameworks. After merging this, we could delete the release and tag and re-push a new tag.

@stevensJourney
stevensJourney marked this pull request as ready for review July 27, 2026 11:56
@stevensJourney
stevensJourney requested a review from simolus3 July 27, 2026 11:56

@simolus3 simolus3 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Retagging sounds good to me since the release is not public yet 👍

@simolus3 simolus3 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just remembered that the release also creates a release to Maven Central, which has already happened for 0.5.0.

So we can't release 0.5.0 again; I see two options here:

  1. Manually attach an XCFramework from the CI run (it's attached via upload-artifact) to the release as a one-off fix.
  2. Bump the version number to 0.5.1 and release again.

We could potentially also do both, with would give us a way to release #204 in a 0.5.1 too.

@stevensJourney

Copy link
Copy Markdown
Contributor Author
  • Manually attach an XCFramework from the CI run (it's attached via upload-artifact) to the release as a one-off fix.
  • Bump the version number to 0.5.1 and release again.

Yeah, let's do this.

@stevensJourney
stevensJourney merged commit d6c157e into main Jul 27, 2026
32 checks passed
@simolus3
simolus3 deleted the fix-release branch July 27, 2026 14:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants