@particle-academy/google-slides-js 0.3.1 → 0.3.3

package/CHANGELOG.md

@@ -8,6 +8,44 @@ 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.3] — 2026-09-11
+
+### Added
+
+- **`fancy-flow-php` executors for every node.** `src/Flow/` carries one `#[FlowNode]` class per action and trigger, and `GoogleSlidesFlow::EXECUTORS` lists them.
+
+A Laravel host running fancy-flow-php could show this connector's nodes in its editor and could not run them: `particle-academy/google-slides-php` shipped the request builders and no executor. Each one is the PHP twin of the executor in `@particle-academy/google-slides-js` — the same kind, the same request, the same value on `out` — and an unsafe-to-replay action derives its idempotency key from the run and the node, so a retried durable run sends the key it sent the first time.
+
+Register them by adding `vendor/particle-academy/google-slides-php/packages/php/src/Flow` to `config('fancy-flow.discover')`. `particle-academy/fancy-flow-php` is SUGGESTED, not required, and conflicts outside `>=0.51.0 <2.0`, the range the executors were tested under. Nothing outside `Flow\` needs it.
+
+### Fixed
+
+- **Fake mode through `ConnectorClient` threw.** `GoogleSlides::descriptor()` handed the connector core its faker as `GoogleSlidesFaker::respond(...)`, which takes `($operation, $request)`; the core calls a faker `($operation, $config, $fake, $input)`. So `$config` arrived as `$request` and every fake call died on "Call to a member function … on null". The descriptor now translates between the two. Calling `GoogleSlidesFaker::respond()` directly — what this package's own tests do, which is why they never saw it — is unchanged.
+
+## [0.3.2] — 2026-09-06
+
+### Changed
+
+- **Published through npm Trusted Publishing, so these packages now carry PROVENANCE.**
+
+Every earlier release went out under a scope-wide npm token. This one is
+published by an OIDC exchange from the release workflow itself, and npm records
+which workflow in which repository built it.
+`npm view @particle-academy/google-slides-ui@0.3.2` shows the attestation; releases before
+this one have none.
+
+What it buys a consumer: the tarball on the registry can be tied to a public
+commit and a public workflow run, rather than to whoever held a token. What it
+does not buy: nothing about the code changed, and the runtime behaviour of all
+four packages is identical to 0.3.1.
+
+- **`repository.directory` in the npm packages.**
+
+`@particle-academy/google-slides-ui` and `@particle-academy/google-slides-js` live at
+`packages/ui` and `packages/js` inside the provider repo. npm's `repository`
+field now says so, which makes the "Repository" link on each package page point
+at the package rather than at the repository root.
+
 ## [0.3.1] — 2026-08-24
 
 ### Fixed

package/package.json

@@ -1,10 +1,11 @@
 {
   "name": "@particle-academy/google-slides-js",
-  "version": "0.3.1",
+  "version": "0.3.3",
   "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.",
   "repository": {
     "type": "git",
-    "url": "git+https://github.com/Fancy-Friends/google-slides.git"
+    "url": "git+https://github.com/Fancy-Friends/google-slides.git",
+    "directory": "packages/js"
   },
   "homepage": "https://github.com/Fancy-Friends/google-slides#readme",
   "bugs": "https://github.com/Fancy-Friends/google-slides/issues",