fancy-google-docs 0.3.0__tar.gz → 0.3.1__tar.gz

{fancy_google_docs-0.3.0 → fancy_google_docs-0.3.1}/CHANGELOG.md

@@ -8,6 +8,31 @@ The four packages share one version, because they are generated from one
 `provider/` definition and a version that meant something different in each
 would be a version nobody could reason about.
 
+## [0.3.1] — 2026-08-24
+
+### Fixed
+
+- **`@particle-academy/google-docs-js` now accepts a RANGE of `@particle-academy/google-docs-ui`, not one exact version.**
+
+It peer-depended on `@particle-academy/google-docs-ui` at exactly the release it shipped with. That is the
+strict form of the thing the kit's own rule forbids — a first-party sibling gets
+a range — and the same block applied the rule correctly to its other two
+dependencies. It was this one pair that slipped.
+
+What it cost: ship `@particle-academy/google-docs-ui` with a fixed help string and every consumer on the
+previous `@particle-academy/google-docs-js` had an **unmet peer**, which npm 7+ errors on. A documentation
+patch could not be delivered without a matching runtime release, and a routine
+`npm update` that moved the ui package alone broke the install.
+
+The coupling is real and is not being loosened away. The ui package emits the
+config schema and the js package implements against it, so a ui that adds a
+field to a js that ignores it is silently wrong. But a PATCH is non-additive by
+definition and a MINOR is where a field can appear — so `>=0.3.1 <0.4.0` is the
+coupling that actually exists rather than the strictest one expressible.
+
+Nothing else changed. `particle-academy/google-docs-php` and `fancy-google-docs` are unaffected; neither has an
+equivalent edge.
+
 ## [0.3.0] — 2026-08-24
 
 ### Added
@@ -93,3 +118,4 @@ create a second document and the action is honestly `unsafe-to-replay`.
 [0.1.0]: https://github.com/Fancy-Friends/google-docs/releases/tag/v0.1.0
 [0.2.0]: https://github.com/Fancy-Friends/google-docs/releases/tag/v0.2.0
 [0.3.0]: https://github.com/Fancy-Friends/google-docs/releases/tag/v0.3.0
+[0.3.1]: https://github.com/Fancy-Friends/google-docs/releases/tag/v0.3.1

{fancy_google_docs-0.3.0 → fancy_google_docs-0.3.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: fancy-google-docs
-Version: 0.3.0
+Version: 0.3.1
 Summary: Google Docs for Python — the service descriptor, its faker, its webhook verification, and one function per operation. Plain HTTP; no vendor SDK.
 Project-URL: Homepage, https://github.com/Fancy-Friends/google-docs
 Project-URL: Issues, https://github.com/Fancy-Friends/google-docs/issues

{fancy_google_docs-0.3.0 → fancy_google_docs-0.3.1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "fancy-google-docs"
-version = "0.3.0"
+version = "0.3.1"
 description = "Google Docs for Python — the service descriptor, its faker, its webhook verification, and one function per operation. Plain HTTP; no vendor SDK."
 readme = "README.md"
 # 3.11 matches fancy-flow-py's floor: 3.10 reaches end of life on 2026-10-31,

{fancy_google_docs-0.3.0 → fancy_google_docs-0.3.1}/src/fancy_google_docs/__init__.py

@@ -21,7 +21,7 @@ from .actions.document_create import document_create
 from .faker import respond
 from .service import BASE_URLS, CONNECTOR_API_VERSION, REQUIRES, SANDBOX, SERVICE, TITLE, descriptor
 
-__version__ = "0.3.0"
+__version__ = "0.3.1"
 
 __all__ = [
     "BASE_URLS",