cassis-cli 3.1.0__tar.gz → 3.1.1__tar.gz

{cassis_cli-3.1.0 → cassis_cli-3.1.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: cassis-cli
-Version: 3.1.0
+Version: 3.1.1
 Summary: Validate, test and evaluate your Cassis context from your terminal, then publish it
 License: Apache-2.0
 License-File: LICENSE
@@ -27,7 +27,7 @@ Validate, test and evaluate your context from your terminal, then publish it. Th
 - `cassis context check` validates the context files in your repository with the exact same checks as the Cassis GitHub PR check (YAML parsing, round-trip, import validation), so you can gate merges in any CI system, not just GitHub. It then prints advisory **context quality warnings** for a tree that parsed: tables not assigned to any domain, joins/metrics pointing at unknown tables or columns, missing table/column descriptions (the same findings `context test` reports, without the agent run). In a checkout bound to a project (`project.yml`, `--project`, or `CASSIS_PROJECT_ID`), it also cross-checks the tree against the project's source schema: references to tables or columns the warehouse doesn't have print as **warnings** too, advisory only (the object may simply not be built or synced yet). Warnings never fail the check.
 - `cassis schema pull` downloads the data source's full source schema (as Cassis last introspected it) into `<base-path>/.schema.json`, a **gitignored** local snapshot (the command maintains the ignore entry) with a `pulled_at` stamp. The warehouse stays authoritative; the snapshot is a cache for offline/bulk work, e.g. a coding agent grepping table and column names during a modeling pass instead of paging through the MCP `get_source_schema` tool. Re-run to refresh.
 - `cassis context fmt` rewrites the context files in canonical form (think `black`/`gofmt` for your context), so hand or agent edits pass the round-trip check.
-- `cassis context upload` uploads the context files to a Cassis project (full replace) and, by default, publishes them immediately as a new version, so a merge to your main branch can go live in one CI step. It runs from a git checkout whose context files are committed, and the published version records that commit, so `cassis status` can tell whether a checkout matches what is live.
+- `cassis context upload` uploads the context files to a Cassis project (full replace) and, by default, publishes them immediately as a new version, so a merge to your main branch can go live in one CI step. It runs from a git checkout whose context files are committed, and the published version records that commit, even when the upload changes nothing, so `cassis status` can tell whether a checkout matches what is live.
 - `cassis context pull` downloads the project's unpublished context into your repository checkout (full sync: stale local context files are pruned), so you can start editing from the current state, or bootstrap a repo that isn't git-synced (e.g. Bitbucket). Pruning only deletes files that are tracked and unmodified in git (i.e. restorable with `git checkout`); untracked or locally modified files are kept and listed, and every deleted path is printed.
 - `cassis context pull` and `cassis context fmt` also write `<base-path>/AGENTS.md`, the Cassis context design guide, into the checkout (default `cassis/AGENTS.md`). It is a managed file (generated banner; the CLI overwrites local edits) so a repo-aware coding agent loads current Cassis modeling doctrine by convention. It sits inside the context directory but is not part of the context tree (which is the YAML files plus the domain Markdown files `domains/**/README.md`), so it is never uploaded, validated, or pruned. Commit it alongside your context changes. The guide text ships inside the CLI package, so its version tracks the **installed cassis-cli version**: upgrade the CLI (`pip install -U cassis-cli`) and re-run `fmt` to pick up doctrine updates; an unpinned `pip install cassis-cli` in CI gets them automatically. The banner stamps a doctrine version, and the CLI never *downgrades* the file: if the checkout's `AGENTS.md` was written by a newer doctrine (a newer CLI, or Cassis itself on a publish), `fmt`/`pull` leave it in place, print an upgrade notice, and `fmt --check` still passes.
 - The CLI identifies itself to the API (`User-Agent: cassis-cli/<version>`), and successful API responses advertise the newest published version. When you are behind, commands print a one-line upgrade notice on stderr (purely informational; output and exit codes are unchanged).

{cassis_cli-3.1.0 → cassis_cli-3.1.1}/README.md

@@ -5,7 +5,7 @@ Validate, test and evaluate your context from your terminal, then publish it. Th
 - `cassis context check` validates the context files in your repository with the exact same checks as the Cassis GitHub PR check (YAML parsing, round-trip, import validation), so you can gate merges in any CI system, not just GitHub. It then prints advisory **context quality warnings** for a tree that parsed: tables not assigned to any domain, joins/metrics pointing at unknown tables or columns, missing table/column descriptions (the same findings `context test` reports, without the agent run). In a checkout bound to a project (`project.yml`, `--project`, or `CASSIS_PROJECT_ID`), it also cross-checks the tree against the project's source schema: references to tables or columns the warehouse doesn't have print as **warnings** too, advisory only (the object may simply not be built or synced yet). Warnings never fail the check.
 - `cassis schema pull` downloads the data source's full source schema (as Cassis last introspected it) into `<base-path>/.schema.json`, a **gitignored** local snapshot (the command maintains the ignore entry) with a `pulled_at` stamp. The warehouse stays authoritative; the snapshot is a cache for offline/bulk work, e.g. a coding agent grepping table and column names during a modeling pass instead of paging through the MCP `get_source_schema` tool. Re-run to refresh.
 - `cassis context fmt` rewrites the context files in canonical form (think `black`/`gofmt` for your context), so hand or agent edits pass the round-trip check.
-- `cassis context upload` uploads the context files to a Cassis project (full replace) and, by default, publishes them immediately as a new version, so a merge to your main branch can go live in one CI step. It runs from a git checkout whose context files are committed, and the published version records that commit, so `cassis status` can tell whether a checkout matches what is live.
+- `cassis context upload` uploads the context files to a Cassis project (full replace) and, by default, publishes them immediately as a new version, so a merge to your main branch can go live in one CI step. It runs from a git checkout whose context files are committed, and the published version records that commit, even when the upload changes nothing, so `cassis status` can tell whether a checkout matches what is live.
 - `cassis context pull` downloads the project's unpublished context into your repository checkout (full sync: stale local context files are pruned), so you can start editing from the current state, or bootstrap a repo that isn't git-synced (e.g. Bitbucket). Pruning only deletes files that are tracked and unmodified in git (i.e. restorable with `git checkout`); untracked or locally modified files are kept and listed, and every deleted path is printed.
 - `cassis context pull` and `cassis context fmt` also write `<base-path>/AGENTS.md`, the Cassis context design guide, into the checkout (default `cassis/AGENTS.md`). It is a managed file (generated banner; the CLI overwrites local edits) so a repo-aware coding agent loads current Cassis modeling doctrine by convention. It sits inside the context directory but is not part of the context tree (which is the YAML files plus the domain Markdown files `domains/**/README.md`), so it is never uploaded, validated, or pruned. Commit it alongside your context changes. The guide text ships inside the CLI package, so its version tracks the **installed cassis-cli version**: upgrade the CLI (`pip install -U cassis-cli`) and re-run `fmt` to pick up doctrine updates; an unpinned `pip install cassis-cli` in CI gets them automatically. The banner stamps a doctrine version, and the CLI never *downgrades* the file: if the checkout's `AGENTS.md` was written by a newer doctrine (a newer CLI, or Cassis itself on a publish), `fmt`/`pull` leave it in place, print an upgrade notice, and `fmt --check` still passes.
 - The CLI identifies itself to the API (`User-Agent: cassis-cli/<version>`), and successful API responses advertise the newest published version. When you are behind, commands print a one-line upgrade notice on stderr (purely informational; output and exit codes are unchanged).

{cassis_cli-3.1.0 → cassis_cli-3.1.1}/cassis_cli/ontology.py

@@ -375,7 +375,13 @@ def upload(
             f"{result['join_count']} joins, {result['metric_count']} metrics"
         )
         version = result.get("published_version")
-        if version is not None:
+        if version is not None and result.get("unchanged"):
+            typer.secho(
+                f"✓ Context uploaded ({counts}). No change: v{version} stays published, "
+                f"and now records commit {head[:9]}.",
+                fg=typer.colors.GREEN,
+            )
+        elif version is not None:
             typer.secho(f"✓ Context uploaded and published as v{version} ({counts}).", fg=typer.colors.GREEN)
         else:
             typer.secho(

{cassis_cli-3.1.0 → cassis_cli-3.1.1}/cassis_cli/status.py

@@ -71,12 +71,25 @@ def _local_comparison(path: Path, head: Optional[str], published_sha: Optional[s
     return f"diverged from the published commit {published_sha[:9]}", False
 
 
+def _published_commit(published: "dict[str, Any]") -> Optional[str]:
+    """The newest commit known to hold the published content.
+
+    An upload that changes nothing publishes no version but moves
+    `latest_git_commit_sha` forward. Servers older than that field only send
+    `git_commit_sha`, the commit the version was published from.
+    """
+    return published.get("latest_git_commit_sha") or published.get("git_commit_sha")
+
+
 def _render(status_record: "dict[str, Any]", comparison_text: str) -> None:
     published = status_record.get("published_version")
     if published:
         label = f" {published['label']!r}" if published.get("label") else ""
         sha = published.get("git_commit_sha")
+        latest = _published_commit(published)
         sha_text = f", commit {sha[:9]}" if sha else ""
+        if latest and latest != sha:
+            sha_text += f", unchanged at {latest[:9]}"
         typer.echo(f"Published: v{published['version']}{label} ({published.get('published_at')}{sha_text})")
     else:
         typer.echo("Published: nothing yet")
@@ -164,7 +177,7 @@ def status(
         """The status record plus the local comparison it implies: (record, comparison_text, in_sync)."""
         record = get_project_status(api_url=api_url, api_key=api_key, project_id=project_id)
         published = record.get("published_version") or {}
-        comparison_text, in_sync = _local_comparison(path, head, published.get("git_commit_sha"))
+        comparison_text, in_sync = _local_comparison(path, head, _published_commit(published))
         return record, comparison_text, in_sync
 
     def report(snapshot: "Tuple[dict[str, Any], str, bool]") -> None:
@@ -175,7 +188,7 @@ def status(
             _render(record, comparison_text)
         else:
             published = record.get("published_version") or {}
-            published_sha = published.get("git_commit_sha")
+            published_sha = _published_commit(published)
             version_text = f"v{published['version']}" if published else "nothing published"
             line = f"{version_text} (commit {published_sha[:9] if published_sha else 'none'}); local: {comparison_text}"
             if line != last_line["text"]:

{cassis_cli-3.1.0 → cassis_cli-3.1.1}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "cassis-cli"
-version = "3.1.0"
+version = "3.1.1"
 description = "Validate, test and evaluate your Cassis context from your terminal, then publish it"
 readme = "README.md"
 license = { text = "Apache-2.0" }