@particle-academy/fancy-connector-core 0.5.0 → 0.6.1

package/CHANGELOG.md

@@ -6,6 +6,57 @@ All notable changes to `fancy-connector-core` are documented here, in
 **This package is pre-1.0, so breaking changes land in MINOR releases.** The
 version number is not a promise it can keep yet; the entries below are.
 
+## [0.6.1] - 2026-09-13
+
+### Fixed
+
+- **`ConnectorError` declares `attempts` and `idempotent` on its type.** A failed
+  call has attached both since 0.5.0, but the class never declared them, so
+  TypeScript refused `error.attempts` and the README taught a cast. They are
+  `declare` fields: nothing changes at runtime, and an error that did not end a
+  call still has no such property. **What to do:** nothing; a cast you added
+  still compiles and can go.
+
+## [0.6.0] - 2026-09-13
+
+Additive only. **What a consumer must DO: nothing** — see each entry.
+
+### Added
+
+- **PHP: the exception a failed call throws now carries `attempts` and
+  `idempotent`**, as the TypeScript error has since 0.1.0. `attempts` is every
+  failed attempt of the call, in order, as `list<Attempt>`; `idempotent` is
+  what the call declared. Without them a PHP host could see *what* failed but
+  not whether a timeout went unretried because the connector is not idempotent
+  or was retried until the budget ran out — which is the difference between
+  *go and look* and *run it again*.
+
+  Both are `null` on any exception that did not end a call — one you construct
+  yourself, one from `HttpErrors::classify()`, and the classified exception
+  chained as `getPrevious()`. Deliberately not `[]` / `false`, which would
+  claim nothing was tried, or that the connector declared a retry unsafe.
+  TypeScript is unchanged: there they stay absent.
+
+  **What a consumer must DO: nothing.** Both are new trailing, optional
+  constructor parameters on `ConnectorException` and
+  `ConnectorRateLimitedException`, so existing `new …Exception(...)` calls,
+  positional or named, keep working. A subclass of `ConnectorException` that
+  declares its own constructor does not need to pass them.
+
+### Changed
+
+- **CI now runs `pint --test` on the PHP tree**, and the tree passes it. Pint
+  was already a dev dependency and `composer lint` already called it, but no
+  workflow did, so three files had drifted (`RenderRules.php`,
+  `ServiceDescriptor.php`, `Socialite/SocialiteBridge.php`) — formatting only,
+  no behaviour change.
+- **Line endings are pinned to LF in `.gitattributes`.** A Windows clone with
+  `core.autocrlf=true` checked every file out as CRLF, which made `pint --test`
+  fail on nearly every PHP file locally while CI saw three, and made
+  `scripts/vendor.mjs` generate a `_connector/` copy whose bytes depended on
+  the machine it ran on. **What a consumer must DO: nothing** — the published
+  files were already LF; only a checkout of this repository changes.
+
 ## [0.5.0] - 2026-09-13
 
 ### Fixed
@@ -371,6 +422,11 @@ clock; this package is the runtime it is written on.
   satisfies it with no dependency in either direction and a host that has never
   heard of a workflow engine can implement it.
 
-[Unreleased]: https://github.com/Particle-Academy/fancy-connector-core/compare/v0.2.0...HEAD
+[Unreleased]: https://github.com/Particle-Academy/fancy-connector-core/compare/v0.6.0...HEAD
+[0.6.0]: https://github.com/Particle-Academy/fancy-connector-core/compare/v0.5.0...v0.6.0
+[0.5.0]: https://github.com/Particle-Academy/fancy-connector-core/compare/v0.4.0...v0.5.0
+[0.4.0]: https://github.com/Particle-Academy/fancy-connector-core/compare/v0.3.1...v0.4.0
+[0.3.1]: https://github.com/Particle-Academy/fancy-connector-core/compare/v0.3.0...v0.3.1
+[0.3.0]: https://github.com/Particle-Academy/fancy-connector-core/compare/v0.2.0...v0.3.0
 [0.2.0]: https://github.com/Particle-Academy/fancy-connector-core/compare/v0.1.0...v0.2.0
 [0.1.0]: https://github.com/Particle-Academy/fancy-connector-core/releases/tag/v0.1.0

package/README.md

@@ -84,11 +84,15 @@ try {
   error.kind;          // the retry primitive
   error.providerCode;  // only where the service declared `providerCodeFrom`
   error.cause;         // the classified error; for a thrown transport, the original below it
+  error.attempts;      // every failed attempt of the call, in order
+  error.idempotent;    // what the call declared — "never allowed to retry" vs "retries ran out"
 }
 ```
 
 PHP is the same: `ConnectorAuthException`, `->status`, `->providerCode`,
-`->getPrevious()`. A provider's own error code is read only where its
+`->getPrevious()`, `->attempts`, `->idempotent`. The last two are set only on the
+error a call throws; anywhere else they are absent (TS) or `null` (PHP), never
+`[]` or `false`. A provider's own error code is read only where its
 `ServiceDescriptor` says where it lives (`providerCodeFrom`) — Bluesky's `error`
 is a code and Mastodon's `error` is a sentence, so a guess would be wrong in the
 most plausible way available.