Skip to content

Derive the stable tag check from the pinned SQLCIPHER_TAG - #3

Merged
cypherair merged 1 commit into
mainfrom
fix/stable-tag-check
Sep 13, 2026
Merged

cypherair merged 1 commit into
mainfrom
fix/stable-tag-check

Conversation

@cypherair

Copy link
Copy Markdown
Owner

The stable release workflow rejected sqlcipher-xcframework-v4.19.0-cypherair.1 because its tag check hardcoded v4.17.0. The check now derives the expected tag from SQLCIPHER_TAG in scripts/build-sqlcipher-xcframework.sh, so a SQLCipher bump needs no workflow edit. RELEASE_TAG is defined at job level so the failure-cleanup step no longer hits an unbound variable when validation fails early.

Verified locally: the derived pattern accepts ...-v4.19.0-cypherair.<n> and rejects the old version and malformed tags.

Authored with AI assistance (Claude Fable 5.1).

The tag check hardcoded the upstream version, so every SQLCipher bump
silently invalidated stable releases until the workflow was edited too.
It now reads the pinned tag from scripts/build-sqlcipher-xcframework.sh.
RELEASE_TAG is set at job level so the failure cleanup step can run when
validation fails before exporting it.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@cypherair
cypherair merged commit 3d6f851 into main Sep 13, 2026
@cypherair
cypherair deleted the fix/stable-tag-check branch September 13, 2026 04:36
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.

1 participant