fancy-gmail 0.3.0__tar.gz → 0.3.1__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -7,6 +7,31 @@ The four packages share one version, because they are generated from one
7
7
  `provider/` definition and a version that meant something different in each
8
8
  would be a version nobody could reason about.
9
9
 
10
+ ## [0.3.1] — 2026-08-24
11
+
12
+ ### Fixed
13
+
14
+ - **`@particle-academy/gmail-js` now accepts a RANGE of `@particle-academy/gmail-ui`, not one exact version.**
15
+
16
+ It peer-depended on `@particle-academy/gmail-ui` at exactly the release it shipped with. That is the
17
+ strict form of the thing the kit's own rule forbids — a first-party sibling gets
18
+ a range — and the same block applied the rule correctly to its other two
19
+ dependencies. It was this one pair that slipped.
20
+
21
+ What it cost: ship `@particle-academy/gmail-ui` with a fixed help string and every consumer on the
22
+ previous `@particle-academy/gmail-js` had an **unmet peer**, which npm 7+ errors on. A documentation
23
+ patch could not be delivered without a matching runtime release, and a routine
24
+ `npm update` that moved the ui package alone broke the install.
25
+
26
+ The coupling is real and is not being loosened away. The ui package emits the
27
+ config schema and the js package implements against it, so a ui that adds a
28
+ field to a js that ignores it is silently wrong. But a PATCH is non-additive by
29
+ definition and a MINOR is where a field can appear — so `>=0.3.1 <0.4.0` is the
30
+ coupling that actually exists rather than the strictest one expressible.
31
+
32
+ Nothing else changed. `particle-academy/gmail-php` and `fancy-gmail` are unaffected; neither has an
33
+ equivalent edge.
34
+
10
35
  ## [0.3.0] — 2026-08-24
11
36
 
12
37
  ### Added
@@ -127,3 +152,4 @@ which is why `refreshToken` is required rather than optional.
127
152
  [0.1.0]: https://github.com/Fancy-Friends/gmail/releases/tag/v0.1.0
128
153
  [0.2.0]: https://github.com/Fancy-Friends/gmail/releases/tag/v0.2.0
129
154
  [0.3.0]: https://github.com/Fancy-Friends/gmail/releases/tag/v0.3.0
155
+ [0.3.1]: https://github.com/Fancy-Friends/gmail/releases/tag/v0.3.1
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.5
2
2
  Name: fancy-gmail
3
- Version: 0.3.0
3
+ Version: 0.3.1
4
4
  Summary: Gmail for Python — the service descriptor, its faker, its webhook verification, and one function per operation. Plain HTTP; no vendor SDK.
5
5
  Project-URL: Homepage, https://github.com/Fancy-Friends/gmail
6
6
  Project-URL: Issues, https://github.com/Fancy-Friends/gmail/issues
@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
4
4
 
5
5
  [project]
6
6
  name = "fancy-gmail"
7
- version = "0.3.0"
7
+ version = "0.3.1"
8
8
  description = "Gmail for Python — the service descriptor, its faker, its webhook verification, and one function per operation. Plain HTTP; no vendor SDK."
9
9
  readme = "README.md"
10
10
  # 3.11 matches fancy-flow-py's floor: 3.10 reaches end of life on 2026-10-31,
@@ -21,7 +21,7 @@ from .actions.message_send import message_send
21
21
  from .faker import respond
22
22
  from .service import BASE_URLS, CONNECTOR_API_VERSION, REQUIRES, SANDBOX, SERVICE, TITLE, descriptor
23
23
 
24
- __version__ = "0.3.0"
24
+ __version__ = "0.3.1"
25
25
 
26
26
  __all__ = [
27
27
  "BASE_URLS",
File without changes
File without changes
File without changes