sqliac 0.1.2

An alternative to Terraform for SQL databases without using a state.

Publishing Instructions

Prereqs

• PyPI account (+ TestPyPI account for the dry run)
• API token from https://pypi.org/manage/account/token/ — start with an account-scoped token (project-scoped tokens only work after the project exists on PyPI)
• Both package names available: check https://pypi.org/project/sqliac/ and https://pypi.org/project/sqliac-snowflake/

1. Lock the dependency before publishing

Your tool.uv.sources workspace links (sqliac = { workspace = true }) only resolve locally — outside the workspace, pip/uv fall back to dependencies = ["sqliac"] with no version bound. Pin it now, or a future core release can silently break the published adapter wheel with nothing to stop it:

# sqliac_adapters/sqliac_snowflake/pyproject.toml
dependencies = [
    "sqliac>=0.1.0,<0.2",
    "snowflake-connector-python[secure-local-storage]",
    "cryptography",
]

2. Build both from the workspace root

uv build only builds the root project by default in a workspace — target each member explicitly:

rm -rf dist/
uv build --package sqliac
uv build --package sqliac-snowflake
ls dist/   # expect 4 files: sdist + wheel × 2 packages

3. Dry run on TestPyPI first

This is the step that actually catches the entry-point bug from earlier — TestPyPI install is the only way to confirm sqliac-snowflake resolves outside the workspace, since local dev never exercises the plugin-discovery path for real.

export UV_PUBLISH_TOKEN=<testpypi-token>
uv publish --publish-url https://test.pypi.org/legacy/ dist/sqliac-0.1.0*
uv publish --publish-url https://test.pypi.org/legacy/ dist/sqliac_snowflake-0.1.0*

Verify in a throwaway venv:

uv venv /tmp/sqliac-check && source /tmp/sqliac-check/bin/activate
pip install -i https://test.pypi.org/simple/ --extra-index-url https://pypi.org/simple/ sqliac-snowflake
sqliac list   # must print "snowflake" — confirms the entry point resolves outside the workspace

--extra-index-url is needed because your real dependencies (jinja2, snowflake-connector-python, etc.) aren't on TestPyPI.

4. Publish for real — core first

Order matters for the reason above, not for pip resolution (pip doesn't validate a dependency exists at publish time) — but publishing core first means anyone who installs the adapter mid-release-window gets a working dependency instead of a 404.

export UV_PUBLISH_TOKEN=<pypi-token>
uv publish dist/sqliac-0.1.0*
uv publish dist/sqliac_snowflake-0.1.0*

5. Verify the real thing

uv venv /tmp/sqliac-verify && source /tmp/sqliac-verify/bin/activate
pip install sqliac-snowflake
sqliac list

Strategic note, not tactical

Per rule #2 — manual token exports don't scale past release one. Once this works, move to a GitHub Actions workflow using PyPI Trusted Publishing (OIDC — no long-lived token to rotate or leak) triggered on tag push, running the same uv build + uv publish steps above for each package. That's the point where "publish two packages" stops being a thing a human remembers to do correctly in order, and becomes a thing that can't be done wrong.