content-cli 0.2.0__tar.gz → 0.3.3__tar.gz

{content_cli-0.2.0 → content_cli-0.3.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: content-cli
-Version: 0.2.0
+Version: 0.3.3
 Summary: Command-line client for the Content engine (talks to /api/v1).
 Project-URL: Homepage, https://github.com/LatentNoise/content
 Project-URL: Source, https://github.com/LatentNoise/content
@@ -21,7 +21,7 @@ Classifier: Programming Language :: Python :: 3.13
 Classifier: Topic :: Multimedia :: Video
 Classifier: Topic :: Software Development :: Libraries :: Python Modules
 Requires-Python: >=3.11
-Requires-Dist: content-sdk==0.2.0
+Requires-Dist: content-sdk==0.3.3
 Description-Content-Type: text/markdown
 
 # `content` — Content CLI
@@ -34,7 +34,7 @@ there is no parallel contract.
 
 ## Install
 
-Once published, the CLI is an ordinary Python application — nothing to clone:
+The CLI is an ordinary Python application — nothing to clone:
 
 ```bash
 uv tool install content-cli     # isolated, on your PATH — recommended
@@ -44,23 +44,12 @@ content --help
 pipx install content-cli
 ```
 
-`content-cli` pulls `content-sdk` from PyPI as an ordinary dependency, pinned
-to the matching release.
-
-> **Not published yet.** Until the first publication the packages are attached
-> to each GitHub release as wheels; see *From a release* below. The commands
-> above are what will work afterwards.
-
-### From a release (today)
-
-Download `content_sdk-<version>-py3-none-any.whl` and
-`content_cli-<version>-py3-none-any.whl` from the
-[latest release](https://github.com/LatentNoise/content/releases/latest), then:
-
-```bash
-uv tool install ./content_cli-<version>-py3-none-any.whl \
-    --find-links .          # --find-links lets it resolve the SDK beside it
-```
+[`content-cli` on PyPI](https://pypi.org/project/content-cli/) pulls
+[`content-sdk`](https://pypi.org/project/content-sdk/) as an ordinary
+dependency, pinned to the matching release. The wheels are also attached to
+each [GitHub release](https://github.com/LatentNoise/content/releases/latest)
+for air-gapped installs (`uv tool install ./content_cli-<v>-py3-none-any.whl
+--find-links .`).
 
 ### From a clone
 

{content_cli-0.2.0 → content_cli-0.3.3}/README.md

@@ -8,7 +8,7 @@ there is no parallel contract.
 
 ## Install
 
-Once published, the CLI is an ordinary Python application — nothing to clone:
+The CLI is an ordinary Python application — nothing to clone:
 
 ```bash
 uv tool install content-cli     # isolated, on your PATH — recommended
@@ -18,23 +18,12 @@ content --help
 pipx install content-cli
 ```
 
-`content-cli` pulls `content-sdk` from PyPI as an ordinary dependency, pinned
-to the matching release.
-
-> **Not published yet.** Until the first publication the packages are attached
-> to each GitHub release as wheels; see *From a release* below. The commands
-> above are what will work afterwards.
-
-### From a release (today)
-
-Download `content_sdk-<version>-py3-none-any.whl` and
-`content_cli-<version>-py3-none-any.whl` from the
-[latest release](https://github.com/LatentNoise/content/releases/latest), then:
-
-```bash
-uv tool install ./content_cli-<version>-py3-none-any.whl \
-    --find-links .          # --find-links lets it resolve the SDK beside it
-```
+[`content-cli` on PyPI](https://pypi.org/project/content-cli/) pulls
+[`content-sdk`](https://pypi.org/project/content-sdk/) as an ordinary
+dependency, pinned to the matching release. The wheels are also attached to
+each [GitHub release](https://github.com/LatentNoise/content/releases/latest)
+for air-gapped installs (`uv tool install ./content_cli-<v>-py3-none-any.whl
+--find-links .`).
 
 ### From a clone
 

content_cli-0.3.3/content_cli/__init__.py

@@ -0,0 +1,12 @@
+"""content — command-line client for the Content engine."""
+
+from importlib.metadata import PackageNotFoundError, version
+
+# The installed wheel's own version — never a literal. The 0.2.0 release
+# shipped `content --version` answering "0.1.0" because this file carried a
+# hardcoded string that no release tooling rewrote (it was the one version
+# declaration outside `make version`'s lockstep). Metadata cannot drift.
+try:
+    __version__ = version("content-cli")
+except PackageNotFoundError:  # an uninstalled source tree (no dist metadata)
+    __version__ = "0+source"

{content_cli-0.2.0 → content_cli-0.3.3}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "content-cli"
-version = "0.2.0"
+version = "0.3.3"
 description = "Command-line client for the Content engine (talks to /api/v1)."
 readme = "README.md"
 license = "AGPL-3.0-or-later"
@@ -24,7 +24,7 @@ classifiers = [
 # Pinned to the exact SDK release, not a floor: the monorepo ships one version
 # for everything (`make version`), and a CLI resolving to a different SDK than
 # the one it was tested against is precisely the drift that guarantees buys.
-dependencies = ["content-sdk==0.2.0"]
+dependencies = ["content-sdk==0.3.3"]
 
 [project.scripts]
 content = "content_cli.cli:main"

content_cli-0.2.0/content_cli/__init__.py

@@ -1,3 +0,0 @@
-"""content — command-line client for the Content engine."""
-
-__version__ = "0.1.0"