What problem does it solve?
Keeping the vendored arize-phoenix-sqlean package current is error-prone: version pins for SQLite, sqlean, and xxHash must move together, checksums must be verified, and wheel publishing across many platforms can silently break. This Skill encodes the exact procedures and gotchas for safely bumping those pins and touching the publish path.
Core Features & Use Cases
- Coordinated version bumps: Explains which Makefile pins must move together (SQLITE_VERSION with its release year and SHA256, SQLEAN_COMMIT with SQLEAN_VERSION in both Makefile and setup.py, XXHASH_TAG with its commit and hash).
- Automated upstream checks: Documents scripts/check-upstream.sh for detecting and applying new upstream releases, plus the weekly phoenix-sqlean-upstream.yml workflow that opens draft bump PRs.
- Wheel and publishing guidance: Covers the cibuildwheel matrix (cp310-cp314 across Linux, macOS, Windows), trusted PyPI publishing, and release-please tagging constraints.
- Use Case: When a new SQLite release ships, run the check-upstream script with --apply, verify the build chain with make and the test suite, and let CI validate the wheel matrix before release-please tags the publish.
Quick Start
Ask the assistant to bump the bundled SQLite version in packages/phoenix-sqlean and verify the build and tests still pass.