chore(cli): sync package

Source: https://github.com/Evokoa/polygres-private/commit/dd45539bce5831282024c44fa73528817ec4a81d

Author: github-actions[bot]

.github/workflows/ci.yml

@@ -36,5 +36,8 @@ jobs:
       - name: Run lint
         run: ruff check .
 
+      - name: Verify release version
+        run: python tools/verify_release_version.py
+
       - name: Build package
         run: python -m build

.github/workflows/publish-python-cli.yml

@@ -43,12 +43,57 @@ jobs:
       - name: Run tests
         run: python -m pytest
 
+      - name: Verify release version
+        run: |
+          if [[ "$GITHUB_REF" == refs/tags/* ]]; then
+            python tools/verify_release_version.py --tag "$GITHUB_REF_NAME"
+          else
+            python tools/verify_release_version.py
+          fi
+
       - name: Build CLI distribution
         run: |
           rm -rf dist
           python -m build
           python -m twine check dist/*
 
+      - name: Verify clean wheel installation
+        run: |
+          smoke_dir="$RUNNER_TEMP/polygres-cli-wheel-smoke"
+          python -m venv "$smoke_dir"
+          "$smoke_dir/bin/python" -m pip install dist/*.whl
+          "$smoke_dir/bin/python" - <<'PY'
+          import importlib.metadata
+          import os
+          from pathlib import Path
+          import subprocess
+          import sys
+          from polygres_cli import __version__
+
+          expected = importlib.metadata.version("polygres-cli")
+          assert __version__ == expected
+          result = subprocess.run(
+              [str(Path(sys.executable).with_name("polygres")), "--version"],
+              check=True,
+              capture_output=True,
+              env={**os.environ, "POLYGRES_API_BASE_URL": "http://127.0.0.1:9/v1"},
+              text=True,
+          )
+          assert result.stdout.splitlines()[0] == f"polygres {expected}"
+          PY
+
+      - name: Verify clean source distribution installation
+        run: |
+          smoke_dir="$RUNNER_TEMP/polygres-cli-sdist-smoke"
+          python -m venv "$smoke_dir"
+          "$smoke_dir/bin/python" -m pip install dist/*.tar.gz
+          "$smoke_dir/bin/python" - <<'PY'
+          import importlib.metadata
+          from polygres_cli import __version__
+
+          assert __version__ == importlib.metadata.version("polygres-cli")
+          PY
+
       - name: Upload CLI distributions
         uses: actions/upload-artifact@v4
         with:

CHANGELOG.md

@@ -2,68 +2,37 @@
 
 All notable changes to `polygres-cli` are documented in this file.
 
-## 0.2.0 - 2026-07-31
+## 0.2.0 - 2026-08-06
 
 ### Added
 
-- Added the complete `polygres context` namespace for pgContext capabilities,
-  discovery, preflight, collection lifecycle, filters, points, durable
-  operations, aggregates, dense retrieval, text hybrid, graph composition,
-  rank fusion, coupled Joint retrieval, grouping, and recall checks.
-- Added strict shared-contract validation, file and standard-input request
-  handling, mutation idempotency, adaptive durable-operation waiting, exact
-  JSON envelopes, and Context-specific human output.
-- Added `polygres api routes` and `polygres api request` with a bundled,
-  versioned OpenAPI snapshot, strict route and method selection, declared
-  parameters, JSON-schema body validation, schema inspection, dry runs, and
-  JSON output.
-- Added FastAPI schema generation and drift validation for the bundled CLI
-  OpenAPI snapshot.
-- Added server-controlled CLI notices with a public API endpoint, 10-hour local
-  cache, ETag revalidation, version and platform targeting, safe plain-text
-  stderr rendering, `once`/`daily`/`always` display policies, and the static
-  `polygres notices` command.
-- Added `polygres vector configs set-default <config-id>` for selecting the
-  default vector configuration without using the web console.
-- Added direct Runtime API graph access support for graph discovery,
-  configuration, builds, and status checks when
-  `CLI_DIRECT_RUNTIME_GRAPH_ENABLED` is enabled and the control plane grants
-  access.
+- Added `polygres context` commands for configuring, managing, and querying pgContext collections.
+- Added `polygres api routes` and `polygres api request` for exploring and calling supported Runtime API routes.
+- Added CLI notices for product updates and important service information.
+- Added `polygres vector configs set-default <config-id>` for selecting the default vector configuration from the CLI.
 
 ### Changed
 
-- Graph status output now includes activation failure reasons and a concise
-  summary of configuration differences.
-- Graph configuration export and apply flows now canonicalize table identifiers
-  as `id_columns`, while continuing to accept legacy `id_column` input.
-- Authentication contracts are vendored into the package so standalone CLI
-  exports do not depend on an external `polygres-lib` installation.
+- Graph status now explains activation failures and configuration differences.
+- Graph configuration now uses `id_columns` while remaining compatible with existing `id_column` configurations.
 
 ### Fixed
 
-- Graph and vector activation verification failures now return nonzero CLI exit
-  codes instead of appearing successful to automation.
-- Authentication errors no longer expose internal identity-provider details.
+- Graph and vector activation failures now return nonzero exit codes.
+- Authentication errors no longer expose internal service details.
+- CSV imports now work with destination tables protected by row-level security.
+- Project status commands now consistently honor the global `--project` option.
 
 ## 0.1.2 - 2026-07-14
 
 ### Changed
 
 - CSV imports now upload directly to blob staging for improved reliability.
-- CSV upload limits now follow the storage allowance of the selected project
-  tier.
-
-## 0.1.1 - 2026-07-14
-
-### Changed
-
-- Added Python 3.10 to release validation for the standalone CLI package.
+- CSV upload limits now follow the storage allowance of the selected project tier.
 
 ## 0.1.0 - 2026-07-09
 
 ### Added
 
 - Initial standalone `polygres-cli` package.
-- Added browser authentication, project management, connection information,
-  Runtime API key management, CSV imports, migrations, graph/vector/text
-  configuration, readiness checks, JSON output, and stable exit codes.
+- Added browser authentication, project management, connection information, Runtime API key management, CSV imports, migrations, graph/vector/text configuration, readiness checks, JSON output, and stable exit codes.

CONTRIBUTING.md

@@ -46,17 +46,19 @@ Publishing uses GitHub Actions Trusted Publishing. Validate first through
 TestPyPI, then publish a matching `python-cli-vX.Y.Z` tag from the public CLI
 repository. Do not add PyPI API tokens to GitHub secrets.
 
-Before syncing a release to the public CLI repository:
+`pyproject.toml` is the only release-version source. The installed CLI reads
+that distribution metadata for `polygres --version`, login metadata, notices,
+and request headers. Before syncing a release to the public CLI repository:
 
 1. Add the release notes and date to `CHANGELOG.md`.
-2. Update the version in `pyproject.toml` and
-   `src/polygres_cli/cli_client.py`.
-3. Update version assertions in the test suite and public installation
-   documentation.
-4. Run `pytest`, `ruff check .`, `python -m build`, and
+2. Update the version in `pyproject.toml`.
+3. Update public installation documentation that names the released version.
+4. Run `pytest`, `ruff check .`, `python tools/verify_release_version.py`,
+   `python -m build`, and
    `python -m twine check dist/*`.
 5. Validate the release through TestPyPI before creating the matching
-   production tag.
+   `python-cli-vX.Y.Z` production tag. The release workflow rejects a tag that
+   does not exactly match the package version.
 
 ## Scope
 

README.md

@@ -1,153 +1,79 @@
 # Polygres CLI
 
-The Polygres CLI manages Polygres projects from the terminal. It authenticates
-with the control plane and supports project setup, imports, migrations, and
-retrieval configuration. It does not expose database passwords.
+Use the Polygres CLI to manage projects, load data, apply migrations, and configure retrieval from your terminal.
+
+The CLI signs in through the Polygres dashboard. It does not expose database passwords.
+
+- [Documentation](https://docs.polygres.com/cli)
+- [Polygres](https://polygres.com)
 
 ## Install
 
+Install the CLI with pip:
+
 ```bash
 pip install polygres-cli
 ```
 
-For an isolated global installation:
+For an isolated global installation, use pipx:
 
 ```bash
 pipx install polygres-cli
 ```
 
-From the repository root, create an isolated development environment and
-install the CLI in editable mode:
+The installed command is `polygres`.
 
-```bash
-python3 -m venv .venv
-source .venv/bin/activate
-sfw pip install -e packages/python-cli
-polygres context capabilities --help
-```
+## Get started
 
-The command remains `polygres`:
+Sign in, choose a project, and check that it is ready:
 
 ```bash
 polygres login
 polygres whoami
 polygres projects list
 polygres projects use <project-id-or-exact-name>
-polygres env
 polygres ready
 ```
 
-`polygres login` opens the Polygres dashboard for approval and prints a URL for
-headless terminals. Credentials are stored at
-`~/.config/polygres/config.json` with owner-only permissions on POSIX systems.
-Run `polygres logout` to revoke the refresh token and remove local credentials.
+`polygres login` opens the dashboard for approval. On a headless terminal, it prints a URL that you can open in another browser. Run `polygres logout` when you want to revoke the session and remove the local credentials.
+
+## Common workflows
 
-Common project operations:
+### Load data and apply migrations
 
 ```bash
 polygres import csv ./documents.csv --table documents --wait
 polygres migrations apply --file ./001_create_documents.sql
+```
+
+### Configure retrieval
+
+```bash
 polygres graph discover --json > graph.json
 polygres graph config apply --file graph.json
 polygres vector configs list
-polygres vector configs set-default <config-id>
 polygres text configs list
-polygres context capabilities
-polygres context collections list
-polygres api routes
-polygres notices
 ```
 
-AI Search commands use the existing login and selected-project workflow:
+## Version and support
+
+The current published CLI release is [`0.1.2`](https://github.com/Evokoa/polygres-cli/releases/tag/python-cli-v0.1.2).
+
+Useful commands:
 
 ```bash
-polygres login
-polygres projects use <project-id-or-exact-name>
-polygres context sources discover
-polygres context collections create support_docs \
-  --source new-table \
-  --table support_docs \
-  --dimensions 768
-polygres context search support_docs --embedding-file query-embedding.json
-polygres context joint support_docs \
-  --embedding-file query-embedding.json \
-  --query "current guidance" \
-  --semantic-weight 0.6 \
-  --lexical-weight 0.1 \
-  --graph-weight 0.3
+polygres --version
+polygres --help
 ```
 
-Context is the pgContext-backed collection namespace. It does not reuse
-pgvector configurations. Mutations send an idempotency key and wait for their
-durable operation by default; use `--no-wait` to return after acceptance.
-Global `--json`, `--project`, `--quiet`, and `--verbose` flags must precede
-`context`.
+Exit codes distinguish validation (`2`), authentication (`3`), permission (`4`), not found (`5`), conflict (`6`), rate limiting (`7`), service availability (`8`), and missing local tools such as `psql` (`9`).
 
-## Generic API routes
+## CLI and SDK
 
-The `api` namespace exposes control-plane routes from the versioned OpenAPI
-snapshot bundled with the CLI. It supplements the stable high-level commands;
-those commands and their handlers remain registered in Python.
+Install `polygres-cli` for terminal workflows. Install `polygres-sdk` in an application that needs graph, vector, text, or hybrid retrieval. The two packages are independent.
 
-List routes, inspect one operation, validate a dry run, and execute it:
+Users of the former combined `polygres` package should install both packages separately when they need both interfaces.
 
-```bash
-polygres api routes
-polygres --json api routes --method GET
-polygres --json api request /projects/{project_id} --method GET --schema
-polygres --json --project <project-id> api request /projects/{project_id} \
-  --method GET \
-  --dry-run
-polygres --json api request /projects \
-  --method POST \
-  --body '{"name":"Support Search"}'
-```
+## Changelog
 
-Use repeatable `--param NAME=VALUE` options for declared path and query
-parameters. Prefix an ambiguous name with `path:`, `query:`, or `header:`.
-Use `--body-file <path>` for a UTF-8 JSON document, or `--body-file -` to read
-one from standard input.
-
-Only route templates and HTTP methods in the bundled snapshot can execute.
-Full URLs, query strings in the route argument, undeclared parameters,
-unsupported methods, unsafe path values, and bodies that do not satisfy the
-declared JSON schema are rejected before a request is sent.
-
-## CLI notices
-
-After a command succeeds, the CLI checks the configured Polygres API for
-applicable service and release notices. Notice text is written only to standard
-error, so standard output and `--json` remain safe for automation. The response
-is cached for up to 10 hours at `~/.config/polygres/notices.json`. Running
-`polygres --version` forces a conditional refresh, and `polygres notices`
-refreshes and displays all currently applicable notices regardless of their
-normal `once` or `daily` display policy.
-
-The check uses a two-second timeout and never changes a command's exit status.
-Network failures, offline operation, malformed responses, and an unavailable
-notice service are silent. Requests go only to the fixed `/cli/notices` path at
-the configured Polygres API origin. The CLI sends its version, derived release
-channel, operating system, and architecture for targeting. It does not send
-command arguments or command output.
-
-Remote notices are plain text. The CLI strips control and ANSI characters,
-limits title and message lengths, accepts only validated HTTPS links, and uses
-a fixed local renderer. Notices cannot define commands, handlers, formatting,
-or endpoints.
-
-Run `polygres --help` for the full command reference. Exit codes distinguish
-validation (`2`), authentication (`3`), permission (`4`), not found (`5`),
-conflict (`6`), rate limiting (`7`), remote availability (`8`), and missing
-local tools such as `psql` (`9`).
-
-## Relationship to the Python SDK
-
-The CLI is distributed separately from the Python SDK. Install `polygres-sdk` when
-your application needs Runtime API retrieval methods, and install
-`polygres-cli` when you need the terminal command. The CLI has its own
-control-plane client and does not require the SDK.
-
-Users of the former combined `polygres` package should install `polygres-cli`
-and `polygres-sdk` separately.
-
-See [CHANGELOG.md](CHANGELOG.md) for release notes.
+See the [CLI 0.1.2 release notes](https://github.com/Evokoa/polygres-cli/releases/tag/python-cli-v0.1.2) for published changes.

pyproject.toml

@@ -33,7 +33,7 @@ polygres = "polygres_cli.cli:main"
 
 [project.urls]
 Homepage = "https://polygres.com"
-Documentation = "https://docs.evokoa.com/polygres"
+Documentation = "https://docs.polygres.com/cli"
 Repository = "https://github.com/Evokoa/polygres-cli"
 Changelog = "https://github.com/Evokoa/polygres-cli/blob/main/CHANGELOG.md"
 Issues = "https://github.com/Evokoa/polygres-cli/issues"

src/polygres_cli/__init__.py

@@ -1 +1,5 @@
 """Polygres command-line client package."""
+
+from polygres_cli._version import __version__
+
+__all__ = ["__version__"]