@billkit-eu/sdk 0.8.0 → 0.8.1

package/CHANGELOG.md

@@ -10,6 +10,14 @@ so the numbers will diverge after this first release.
 
 ## [Unreleased]
 
+## [0.8.1] - 2026-09-26
+
+### Changed
+- `UpdateCouponParams.applies_to_price_ids` (`null` lifts the price restriction), `UpdateCouponParams.min_amount_cents` (`null` lifts the minimum), `UpdateProductParams.marketing_features` (`null` empties the list) and `UpdatePriceParams.refund_window_initial_days` / `refund_window_renewal_days` (`null` drops the price's override) now accept `null`, sent as a JSON null. The request already carried a `null` through; the types refused it. Every other update field stays typed without `null`.
+  **Upgrade note:** as in 0.8.0, a null passed through from your own data clears the field: `coupons.update(id, { min_amount_cents: row.min })` with `row.min` sometimes `null` now lifts the coupon's minimum, which widens who can redeem it. Omit the field when you mean "leave it".
+  **Requires the matching API release.** An older API accepts the null on `applies_to_price_ids`, `min_amount_cents` and `marketing_features` and leaves the value in place.
+- Every other update field refuses an explicit null with a `400` naming the field (the API used to ignore it). The SDK never sends one there; omit the field to leave it unchanged.
+
 ## [0.8.0] - 2026-09-26
 
 ### Added
@@ -276,7 +284,8 @@ First public release.
   back a one-shot paid with giropay before the shutdown works;
   `OneShotPayment.method` is a plain `string`.
 
-[Unreleased]: https://github.com/billkit-eu/billkit-node/compare/v0.8.0...HEAD
+[Unreleased]: https://github.com/billkit-eu/billkit-node/compare/v0.8.1...HEAD
+[0.8.1]: https://github.com/billkit-eu/billkit-node/compare/v0.8.0...v0.8.1
 [0.8.0]: https://github.com/billkit-eu/billkit-node/compare/v0.7.1...v0.8.0
 [0.7.1]: https://github.com/billkit-eu/billkit-node/compare/v0.7.0...v0.7.1
 [0.7.0]: https://github.com/billkit-eu/billkit-node/compare/v0.6.0...v0.7.0

package/README.md

@@ -113,7 +113,7 @@ The client exposes one accessor per resource family. Each mirrors the verbs from
 
 ### Clearing an optional field
 
-On an update, an explicit `null` clears a field and omitting it leaves the stored value alone. Only `undefined` is pruned from a request body, so `null` reaches the API as a JSON null. This applies to `products.update` (`description`, `default_price_id`), `customers.update` (`name`), `webhookEndpoints.update` (`description`), `coupons.update` (`max_redemptions` removes the cap, `redeem_by` removes the expiry) and `taxRates.update` (`display_name`).
+On an update, an explicit `null` clears a field and omitting it leaves the stored value alone. Only `undefined` is pruned from a request body, so `null` reaches the API as a JSON null. This applies to `products.update` (`description`, `default_price_id`, `marketing_features` empties the list), `prices.update` (`refund_window_initial_days` and `refund_window_renewal_days` drop the price's override), `customers.update` (`name`), `webhookEndpoints.update` (`description`), `coupons.update` (`max_redemptions` removes the cap, `redeem_by` removes the expiry, `applies_to_price_ids` lifts the price restriction, `min_amount_cents` lifts the minimum) and `taxRates.update` (`display_name`). Every other update field is typed without `null`, and the API refuses a null there with a 400 naming the field. A `metadata` update replaces the stored object whole, so `metadata: {}` is how it is emptied.
 
 ### Retiring something, and deleting something
 

package/dist/index.cjs

@@ -999,7 +999,7 @@ function sleep(ms) {
 }
 
 // src/version.ts
-var VERSION = "0.8.0";
+var VERSION = "0.8.1";
 
 // src/transport.ts
 var DEFAULT_BASE_URL = "https://api.billkit.eu";