napkinstack 0.19.2__tar.gz → 0.19.3__tar.gz

{napkinstack-0.19.2 → napkinstack-0.19.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: napkinstack
-Version: 0.19.2
+Version: 0.19.3
 Summary: Engineering framework for several teams and their agents working in one repository: modules, contracts, guardrails in CI.
 License-Expression: MIT
 License-File: LICENSE
@@ -21,7 +21,7 @@ modules, contracts, guardrails in CI. On the Django or Rails model, one command
 the project, which then receives new versions on demand; no application stack is imposed.
 Positioning and vocabulary: [`PRODUCT.md`](PRODUCT.md) §1.
 
-> **Status: v0.19.2, published** on [PyPI](https://pypi.org/project/napkinstack/).
+> **Status: v0.19.3, published** on [PyPI](https://pypi.org/project/napkinstack/).
 > What each version changes, engine and project apart: [`CHANGELOG.md`](CHANGELOG.md).
 > What is open: [`docs/governance/workstreams.md`](docs/governance/workstreams.md).
 
@@ -85,8 +85,8 @@ To try it without installing anything, or to install it from this repository ins
 registry — always pinned to a release tag:
 
 ```bash
-uvx --from "git+https://github.com/NapkinStack/engineering-os@v0.19.2" nstack init my-project
-uv tool install "napkinstack @ git+https://github.com/NapkinStack/engineering-os@v0.19.2"
+uvx --from "git+https://github.com/NapkinStack/engineering-os@v0.19.3" nstack init my-project
+uv tool install "napkinstack @ git+https://github.com/NapkinStack/engineering-os@v0.19.3"
 ```
 
 **Two channels, one published artefact.** The registry publishes: the PyPI artefact of a
@@ -127,8 +127,8 @@ Each project then pins its version and changes it through `nstack update`.
 
 **Prerequisites**: uv and git. The guardrails really block on a public GitHub repository,
 or on a private one under the Team or Pro plan; on a private repository on the Free plan
-CI informs without blocking
-([a clarification of PDR-0001](docs/pdr/0001-create-a-project-and-receive-updates.md)).
+CI informs without blocking, and `doctor` says the repository *unguarded*
+([PDR-0006](docs/pdr/0006-work-where-the-forge-cannot-guard.md)).
 Off GitHub (GitLab, Forgejo, Gitea, another forge or none), the checks are attested on the
 workstation and every command says what it cannot verify ([PDR-0018](docs/pdr/0018-git-is-required-the-forge-is-the-project-s-choice.md)).
 

{napkinstack-0.19.2 → napkinstack-0.19.3}/README.md

@@ -5,7 +5,7 @@ modules, contracts, guardrails in CI. On the Django or Rails model, one command
 the project, which then receives new versions on demand; no application stack is imposed.
 Positioning and vocabulary: [`PRODUCT.md`](PRODUCT.md) §1.
 
-> **Status: v0.19.2, published** on [PyPI](https://pypi.org/project/napkinstack/).
+> **Status: v0.19.3, published** on [PyPI](https://pypi.org/project/napkinstack/).
 > What each version changes, engine and project apart: [`CHANGELOG.md`](CHANGELOG.md).
 > What is open: [`docs/governance/workstreams.md`](docs/governance/workstreams.md).
 
@@ -69,8 +69,8 @@ To try it without installing anything, or to install it from this repository ins
 registry — always pinned to a release tag:
 
 ```bash
-uvx --from "git+https://github.com/NapkinStack/engineering-os@v0.19.2" nstack init my-project
-uv tool install "napkinstack @ git+https://github.com/NapkinStack/engineering-os@v0.19.2"
+uvx --from "git+https://github.com/NapkinStack/engineering-os@v0.19.3" nstack init my-project
+uv tool install "napkinstack @ git+https://github.com/NapkinStack/engineering-os@v0.19.3"
 ```
 
 **Two channels, one published artefact.** The registry publishes: the PyPI artefact of a
@@ -111,8 +111,8 @@ Each project then pins its version and changes it through `nstack update`.
 
 **Prerequisites**: uv and git. The guardrails really block on a public GitHub repository,
 or on a private one under the Team or Pro plan; on a private repository on the Free plan
-CI informs without blocking
-([a clarification of PDR-0001](docs/pdr/0001-create-a-project-and-receive-updates.md)).
+CI informs without blocking, and `doctor` says the repository *unguarded*
+([PDR-0006](docs/pdr/0006-work-where-the-forge-cannot-guard.md)).
 Off GitHub (GitLab, Forgejo, Gitea, another forge or none), the checks are attested on the
 workstation and every command says what it cannot verify ([PDR-0018](docs/pdr/0018-git-is-required-the-forge-is-the-project-s-choice.md)).
 

{napkinstack-0.19.2 → napkinstack-0.19.3}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "napkinstack"
-version = "0.19.2"
+version = "0.19.3"
 description = "Engineering framework for several teams and their agents working in one repository: modules, contracts, guardrails in CI."
 requires-python = ">=3.12"
 license = "MIT"

{napkinstack-0.19.2 → napkinstack-0.19.3}/pyproject.toml.orig

@@ -1,6 +1,6 @@
 [project]
 name = "napkinstack"
-version = "0.19.2"
+version = "0.19.3"
 description = "Engineering framework for several teams and their agents working in one repository: modules, contracts, guardrails in CI."
 requires-python = ">=3.12"
 license = "MIT"