Tag a release for the SQLCipher 4.18.0 update already on main

[diskude]

Thanks for keeping this package current — the daily update-sqlcipher.yml PR flow is great to depend on.

main has picked up two changes since the 1.11.0 tag (37a2581, 2026-07-08), but neither is reachable from a tagged release yet:

• Define NDEBUG for release builds of the SQLCipher C target #20 — Define NDEBUG for release builds of the SQLCipher C target (merged 2026-07-30)
• Update to SQLCipher 4.18.0 and SQLite 3.53.4 #21 — Update to SQLCipher 4.18.0 / SQLite 3.53.4 (merged 2026-08-18) — upstream notes

SwiftPM consumers that pin an exact release (we use .package(url: ..., exact: "1.11.0")) can't resolve to main, so the 4.18.0 update isn't available to us today.

In the previous cycles the release tag followed the update PR the same day — 4.17.0 (#19) → 1.11.0 on 2026-07-08, 4.16.0 (#17) → 1.10.0 on 2026-05-12, 4.15.0 (#16) → 1.9.0 on 2026-04-28 — so this looks like it may simply have been missed rather than intentionally held back.

Would you consider cutting a 1.12.0 release from main (0f4d13a)?

If it would help, I'm happy to open a PR adding a tag/release step to update-sqlcipher.yml so future SQLCipher bumps publish a release automatically — but I didn't want to touch your release process uninvited.

[marcprux]

Thanks for the nudge! I seem to have gotten distracted between merging the PR and make a new release.

1.12.0 is now tagged and released: https://github.com/skiptools/swift-sqlcipher/releases/tag/1.12.0