fancy-buffer 0.1.0__tar.gz → 0.1.2__tar.gz

fancy_buffer-0.1.2/CHANGELOG.md

@@ -0,0 +1,72 @@
+# Changelog
+
+All notable changes to `@particle-academy/buffer-ui`,
+`@particle-academy/buffer-js`, `particle-academy/buffer-php` and
+`fancy-buffer`.
+
+## [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
+
+- **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/buffer-ui@0.1.1` 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.1.0.
+
+- **`repository.directory` in the npm packages.**
+
+`@particle-academy/buffer-ui` and `@particle-academy/buffer-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.1.0] — 2026-08-23
+
+First release.
+
+### Added
+
+- `post_create` — create, queue or immediately share a text post through
+  Buffer's current GraphQL API.
+- A GraphQL PostActionSuccess faker for development without creating a real
+  post.
+
+### Current API, not legacy REST
+
+The connector targets `POST https://api.buffer.com` with a JSON GraphQL
+envelope. The historical form-encoded `api.bufferapp.com/1` API is not used.
+
+### OAuth safety
+
+Buffer requires S256 PKCE for every App Client. Access tokens last one hour and
+refresh tokens rotate on every use; replaying an old refresh token revokes the
+entire grant.
+
+### No sandbox or idempotency guarantee
+
+Buffer has no separate test estate, and `createPost` documents no idempotency
+key. A retry may create or publish the post twice.
+
+[0.1.0]: https://github.com/Fancy-Friends/buffer/releases/tag/v0.1.0

{fancy_buffer-0.1.0 → fancy_buffer-0.1.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: fancy-buffer
-Version: 0.1.0
+Version: 0.1.2
 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.0 → fancy_buffer-0.1.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "fancy-buffer"
-version = "0.1.0"
+version = "0.1.2"
 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.0 → fancy_buffer-0.1.2}/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.0"
+__version__ = "0.1.2"
 
 __all__ = [
     "BASE_URLS",

fancy_buffer-0.1.0/CHANGELOG.md

@@ -1,34 +0,0 @@
-# Changelog
-
-All notable changes to `@particle-academy/buffer-ui`,
-`@particle-academy/buffer-js`, `particle-academy/buffer-php` and
-`fancy-buffer`.
-
-## [0.1.0] — 2026-08-23
-
-First release.
-
-### Added
-
-- `post_create` — create, queue or immediately share a text post through
-  Buffer's current GraphQL API.
-- A GraphQL PostActionSuccess faker for development without creating a real
-  post.
-
-### Current API, not legacy REST
-
-The connector targets `POST https://api.buffer.com` with a JSON GraphQL
-envelope. The historical form-encoded `api.bufferapp.com/1` API is not used.
-
-### OAuth safety
-
-Buffer requires S256 PKCE for every App Client. Access tokens last one hour and
-refresh tokens rotate on every use; replaying an old refresh token revokes the
-entire grant.
-
-### No sandbox or idempotency guarantee
-
-Buffer has no separate test estate, and `createPost` documents no idempotency
-key. A retry may create or publish the post twice.
-
-[0.1.0]: https://github.com/Fancy-Friends/buffer/releases/tag/v0.1.0