planvortex 0.9.0__tar.gz → 0.11.0__tar.gz

{planvortex-0.9.0 → planvortex-0.11.0}/CHANGELOG.md

@@ -4,6 +4,113 @@ All notable changes to this package are documented here. The format follows
 [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this project adheres to
 [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.11.0] - 2026-09-29
+
+A connected **WooCommerce store** becomes a source for the AI planner: the `from_catalog` template
+can now write a week of posts from the store's real products (name, description, price, picture and
+the link to its page), not only from a Meta catalogue. Nothing was removed and no signature moved:
+upgrading from `0.10.0` needs no changes, and `MIGRATION.md` gains no entry.
+
+### Added
+
+- **`pv.integrations.products(id_organization, id_integration, cursor=, search=, limit=)`**, over
+  `GET /organizations/{id}/integrations/{id}/products`: one page of a connected store's catalogue,
+  to choose the products of a plan. Also on the synchronous client. Four things about it are not
+  obvious, and all four are in its docstring:
+  - **It pages by an opaque cursor**, not by number: send `next_cursor` back as `cursor` exactly as
+    it came. There is no `iterate_products` on purpose: every page is a live request to the
+    client's own hosting, and finding three products among ten thousand is what `search` is for.
+  - **Out-of-stock products come back with `available: False`**: show them, but do not let them be
+    chosen, or the plan is refused with 2112.
+  - **`price` is text to copy verbatim**, as the store displays it (tax, symbol, range). Absent
+    means no price.
+  - A store that rejects its key (2211) is marked until it is reconnected; a firewall (2212) or a
+    store that does not answer (2213) is not.
+- **`url=` and `id_integration=` on `integrations.connect_link`.** The store's approval button: the
+  link points at the store's own WordPress, so it needs its address, and `id_integration`
+  reconnects a store instead of adding one. After approving, the user comes back with an
+  `id_integration`: **read that integration instead of trusting `success`** (2219 means the key is
+  still being checked).
+- **`"provider": "woocommerce"` in `integrations.connect`**, with a read-only key created by hand
+  (`url`, `consumer_key`, `consumer_secret`). It is the way when the store uses plain permalinks and
+  the button cannot work (2216).
+- **`source["id_integration_catalog"]`** on `ai_plans.create`: the store a `from_catalog` plan
+  reads from, exclusive with `id_account_catalog` (both at once is a 2112). The stored products gain
+  `permalink`, the product's page, which the texts use where a link can be clicked and where a
+  Pinterest pin leads unless the plan has its own `options["link"]`.
+- **`unsupported_networks`** on `PlannerTemplate`: the networks whose accounts a plan of that
+  template cannot carry. A plan with one is refused with **2120** before anything is read or
+  charged; today that is YouTube on `from_images` and `from_catalog`.
+- On `IntegrationProvider`, the gates `connect_link`, `connect_link_fields` and `catalog`. **Having a
+  link is not being OAuth**: branch on these, never on the provider's name.
+- Types `IntegrationCatalogProduct`, `IntegrationCatalogPage`, `IntegrationConfig`,
+  `IntegrationFormField` and `WooCommerceConnectRequest`; `"woocommerce"` in
+  `INTEGRATION_PROVIDERS`.
+
+### Changed
+
+- **`Integration["config"]` is typed as `IntegrationConfig`**, which adds the store's keys to the
+  feed's: `api_base`, `auth_mode`, `key_ending`, `currency` and `tax_location_missing`. Two of them
+  have to be shown, not just stored. `key_ending` is how the user finds the key to delete in their
+  WordPress after disconnecting, because **WooCommerce does not let an app revoke its own key**; and
+  `tax_location_missing: True` means the store's API gives prices without tax labelled as tax
+  included, so its taxable products come without a price until the store's setting is fixed and it
+  is reconnected. `RssConfig` stays what an `update` takes, and a store's `config` cannot be edited
+  at all (2220).
+- A form field can now be of type `secret` (WooCommerce's consumer secret): mask it, never prefill
+  it, and mark it as a new password so the browser does not fill it with the user's own.
+
+## [0.10.0] - 2026-09-24
+
+Pinterest, the fourteenth network, reaches the package — and it is the first one where choosing
+the account does not choose where the publication comes out. **A pin goes to a board**, and that is
+a field no other network has. Nothing was removed and no signature moved: upgrading from `0.9.0`
+needs no changes, and `MIGRATION.md` gains no entry. The new fields are optional for the other
+thirteen networks.
+
+**`PublishableNetwork` is a closed `Literal` written by hand, and it went red on regeneration** —
+which is how it is meant to find out. Pinterest is also the first network that enters
+`PUBLISHABLE_NETWORKS` and **not** `COMMENT_NETWORKS`, so it is the first real proof that the two
+lists are independent.
+
+### Added
+
+- **`pv.accounts.destinations(id_organization, id_account)`** and
+  **`pv.accounts.destination(id_organization, id_account, id_destination)`**, over
+  `GET /organizations/{id}/accounts/{id}/destinations[/{id}]`: an account's Pinterest boards, and
+  one board with its sections. Every other network answers 992 — the account itself is where its
+  publications go. Both take `refresh=True` to skip the server's short cache, for a board created
+  a moment ago; not on every call, because all of PlanVortex's Pinterest traffic leaves through one
+  application. Also on the synchronous client.
+- **`"pinterest"` in `PublishableNetwork` and `PUBLISHABLE_NETWORKS`**, and **`destination` and
+  `link` on `PublicationInput`.** On Pinterest the board is **required**, and leaving it out does
+  not raise: the publication is created in `withErrors` with code 987 and is never attempted.
+  `destination["id"]` is **always a string** — Pinterest's ids are long integers. `link` is where
+  the pin takes whoever clicks it: it goes in its own field, not inside `text`. On every other
+  network both fields are deleted on save. Ask `destinations` and `link` in
+  `catalog.social_capabilities()` rather than keeping a list of which network has which.
+- **`destinations` on `AiPlanCreateRequest` and `AiPlan`, and `options["link"]`.** A plan with a
+  Pinterest account needs that account's board, one entry per account; without it
+  `ai_plans.create` raises **2118**, listing every account that fails. A plan that would leave pins
+  without an image is refused with **2119** before a single credit is spent, and an image that
+  fails halfway through the generation shows up as a **922** in `warnings`, with the publication
+  that was left without it.
+- Types `Destination`, `PublicationDestination` and `AiPlanDestination`.
+
+### Fixed
+
+- **Pinterest's error codes (987-996) arrived outside every family**, the third time a network's
+  codes were born above the ceiling of the publications range (after 978 and 980). They are now
+  `PublicationError`. The one that matters most is **991**: Pinterest throttling the application,
+  sent as HTTP 429 with `Retry-After` — the answer is to wait, and `error.retry_after` says how long.
+- **547, 548 and 716 were unclassified too.** 547 (a client app's identifier cannot change) and
+  548 (rotating the secret failed, the method that came with `0.9.0`) are now `AuthError`, and 716
+  (another process is renewing the Bluesky session; retry) is `AccountError`.
+- A test now checks that **every** error code named in the specification's error tables falls into
+  some family, so the next network cannot repeat this without the build going red.
+- The prose that counts networks said "nine of the eleven" and "eleven and not twelve" in places;
+  it now says fourteen, thirteen of which publish.
+
 ## [0.9.0] - 2026-09-17
 
 **Which AI plan worked?** The server can now answer it, and so can this package:

{planvortex-0.9.0 → planvortex-0.11.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: planvortex
-Version: 0.9.0
+Version: 0.11.0
 Summary: Official Python client for the PlanVortex API
 Project-URL: Homepage, https://planvortex.com/en/developers
 Project-URL: Documentation, https://taliasoftworks.github.io/PlanVortexPython/
@@ -242,11 +242,11 @@ memorising numbers:
 
 | Codes | Family | Exception |
 |---|---|---|
-| 500-546 | `auth` | `AuthError` |
+| 500-548 | `auth` | `AuthError` |
 | 601-612 | `user` | `UserError` |
-| 700-715 | `account` | `AccountError` |
+| 700-716 | `account` | `AccountError` |
 | 800-810 | `file` | `FileError` |
-| 900-986 | `publication` | `PublicationError` |
+| 900-996 | `publication` | `PublicationError` |
 | 1000-1003 | `general` | `PlanVortexError` |
 | 1100-1111 | `organization` | `OrganizationError` |
 | 1200-1207 | `role` | `PlanVortexError` |

{planvortex-0.9.0 → planvortex-0.11.0}/README.md

@@ -212,11 +212,11 @@ memorising numbers:
 
 | Codes | Family | Exception |
 |---|---|---|
-| 500-546 | `auth` | `AuthError` |
+| 500-548 | `auth` | `AuthError` |
 | 601-612 | `user` | `UserError` |
-| 700-715 | `account` | `AccountError` |
+| 700-716 | `account` | `AccountError` |
 | 800-810 | `file` | `FileError` |
-| 900-986 | `publication` | `PublicationError` |
+| 900-996 | `publication` | `PublicationError` |
 | 1000-1003 | `general` | `PlanVortexError` |
 | 1100-1111 | `organization` | `OrganizationError` |
 | 1200-1207 | `role` | `PlanVortexError` |