@particle-academy/google-slides-js 0.3.0 → 0.3.1
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.
- package/CHANGELOG.md +26 -0
- package/package.json +2 -2
package/CHANGELOG.md
CHANGED
|
@@ -8,6 +8,31 @@ The four packages share one version, because they are generated from one
|
|
|
8
8
|
`provider/` definition and a version that meant something different in each
|
|
9
9
|
would be a version nobody could reason about.
|
|
10
10
|
|
|
11
|
+
## [0.3.1] — 2026-08-24
|
|
12
|
+
|
|
13
|
+
### Fixed
|
|
14
|
+
|
|
15
|
+
- **`@particle-academy/google-slides-js` now accepts a RANGE of `@particle-academy/google-slides-ui`, not one exact version.**
|
|
16
|
+
|
|
17
|
+
It peer-depended on `@particle-academy/google-slides-ui` at exactly the release it shipped with. That is the
|
|
18
|
+
strict form of the thing the kit's own rule forbids — a first-party sibling gets
|
|
19
|
+
a range — and the same block applied the rule correctly to its other two
|
|
20
|
+
dependencies. It was this one pair that slipped.
|
|
21
|
+
|
|
22
|
+
What it cost: ship `@particle-academy/google-slides-ui` with a fixed help string and every consumer on the
|
|
23
|
+
previous `@particle-academy/google-slides-js` had an **unmet peer**, which npm 7+ errors on. A documentation
|
|
24
|
+
patch could not be delivered without a matching runtime release, and a routine
|
|
25
|
+
`npm update` that moved the ui package alone broke the install.
|
|
26
|
+
|
|
27
|
+
The coupling is real and is not being loosened away. The ui package emits the
|
|
28
|
+
config schema and the js package implements against it, so a ui that adds a
|
|
29
|
+
field to a js that ignores it is silently wrong. But a PATCH is non-additive by
|
|
30
|
+
definition and a MINOR is where a field can appear — so `>=0.3.1 <0.4.0` is the
|
|
31
|
+
coupling that actually exists rather than the strictest one expressible.
|
|
32
|
+
|
|
33
|
+
Nothing else changed. `particle-academy/google-slides-php` and `fancy-google-slides` are unaffected; neither has an
|
|
34
|
+
equivalent edge.
|
|
35
|
+
|
|
11
36
|
## [0.3.0] — 2026-08-24
|
|
12
37
|
|
|
13
38
|
### Added
|
|
@@ -94,3 +119,4 @@ can create a second presentation and the action is honestly
|
|
|
94
119
|
[0.1.0]: https://github.com/Fancy-Friends/google-slides/releases/tag/v0.1.0
|
|
95
120
|
[0.2.0]: https://github.com/Fancy-Friends/google-slides/releases/tag/v0.2.0
|
|
96
121
|
[0.3.0]: https://github.com/Fancy-Friends/google-slides/releases/tag/v0.3.0
|
|
122
|
+
[0.3.1]: https://github.com/Fancy-Friends/google-slides/releases/tag/v0.3.1
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@particle-academy/google-slides-js",
|
|
3
|
-
"version": "0.3.
|
|
3
|
+
"version": "0.3.1",
|
|
4
4
|
"description": "Google Slides for Node — the service descriptor, its faker, its webhook verification, and one function per operation. Plain HTTP on @particle-academy/fancy-connector-core; no vendor SDK.",
|
|
5
5
|
"repository": {
|
|
6
6
|
"type": "git",
|
|
@@ -52,7 +52,7 @@
|
|
|
52
52
|
},
|
|
53
53
|
"peerDependencies": {
|
|
54
54
|
"@particle-academy/fancy-flow": ">=0.47.1 <2.0",
|
|
55
|
-
"@particle-academy/google-slides-ui": "0.3.0"
|
|
55
|
+
"@particle-academy/google-slides-ui": ">=0.3.0 <0.4.0"
|
|
56
56
|
},
|
|
57
57
|
"peerDependenciesMeta": {
|
|
58
58
|
"@particle-academy/fancy-flow": {
|