fancy-buffer 0.1.1__tar.gz → 0.1.3__tar.gz

{fancy_buffer-0.1.1 → fancy_buffer-0.1.3}/CHANGELOG.md

@@ -4,6 +4,26 @@ All notable changes to `@particle-academy/buffer-ui`,
 `@particle-academy/buffer-js`, `particle-academy/buffer-php` and
 `fancy-buffer`.
 
+## [0.1.3] — 2026-09-12
+
+### Changed
+
+- **Requires `fancy-connector-core` ≥ 0.4.0** — `particle-academy/fancy-connector-core` for php, `@particle-academy/fancy-connector-core` for js. The flow executors now pass a provider's declared `idempotencyMaxLength` through to the core's key derivation, and a named argument an older core does not accept is a fatal rather than a no-op, so the floor moves with it. This connector declares no limit and passes nothing, so nothing else changes for it; the bump is the floor alone.
+
+## [0.1.2] — 2026-09-11
+
+### Added
+
+- **`fancy-flow-php` executors for every node.** `src/Flow/` carries one `#[FlowNode]` class per action and trigger, and `BufferFlow::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/buffer-php` shipped the request builders and no executor. Each one is the PHP twin of the executor in `@particle-academy/buffer-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/buffer-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.** `Buffer::descriptor()` handed the connector core its faker as `BufferFaker::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 `BufferFaker::respond()` directly — what this package's own tests do, which is why they never saw it — is unchanged.
+
 ## [0.1.1] — 2026-09-06
 
 ### Changed

{fancy_buffer-0.1.1 → fancy_buffer-0.1.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: fancy-buffer
-Version: 0.1.1
+Version: 0.1.3
 Summary: Buffer 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/buffer
 Project-URL: Issues, https://github.com/Fancy-Friends/buffer/issues

{fancy_buffer-0.1.1 → fancy_buffer-0.1.3}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "fancy-buffer"
-version = "0.1.1"
+version = "0.1.3"
 description = "Buffer 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_buffer-0.1.1 → fancy_buffer-0.1.3}/src/fancy_buffer/__init__.py

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