@spree/docs 0.1.147 → 0.1.148

package/dist/developer/core-concepts/payments.md

@@ -80,10 +80,6 @@ erDiagram
         integer refund_reason_id
     }
 
-    LogEntry {
-        text details
-    }
-
     Order ||--o{ Payment : "has many"
     Order ||--o{ PaymentSession : "has many"
     Payment }o--|| PaymentMethod : "belongs to"
@@ -91,7 +87,6 @@ erDiagram
     Payment }o--o| PaymentSource : "source"
     Payment }o--o| StoreCredit : "source"
     Payment ||--o| PaymentSession : "linked via response_code"
-    Payment ||--o{ LogEntry : "has many"
     Payment ||--o{ Refund : "has many"
     PaymentMethod ||--o{ PaymentSession : "has many"
     PaymentMethod ||--o{ PaymentSetupSession : "has many"
@@ -509,11 +504,7 @@ Each payment update also recalculates the order's `payment_state`:
 | `credit_owed` | This order has been paid for in excess of its total |
 | `paid` | This order has been paid for in full |
 
-> **WARNING:** You may want to keep tabs on the number of orders with a `payment_state` of `failed`. A sudden increase could indicate a problem with your payment gateway and most likely a serious problem affecting customer satisfaction. Check the latest `log_entries` for the most recent payments if this is happening.
-
-### Log Entries
-
-Responses from payment gateways are stored as log entries for debugging purposes. These can be viewed in the Admin Panel on the payment detail page.
+> **WARNING:** You may want to keep tabs on the number of orders with a `payment_state` of `failed`. A sudden increase could indicate a problem with your payment gateway and most likely a serious problem affecting customer satisfaction. Check your payment gateway's dashboard for the most recent transactions if this is happening.
 
 ## Payment Sources
 

package/dist/developer/upgrades/5.6-to-6.0.md

@@ -344,6 +344,16 @@ Also note:
 - Localized number parsing still happens: `Spree::Price#amount=` runs `Spree::LocalizedNumber.parse`, so `set_price(currency, '1,599.99')` works as `price=` did.
 - The variant validation that inferred a missing price from the product's default variant is gone. Set prices explicitly (the product and variant factories already do).
 
+### `StateChange` and `LogEntry` are gone
+
+`Spree::StateChange` and `Spree::LogEntry` are removed — the models, the `state_changes` associations on `Order`, `Payment` and `Fulfillment`, the `log_entries` associations on `Payment` and `Refund`, and everything that wrote to them. Both were write-only: nothing in Spree read the rows back, and the admin screens that displayed them are gone.
+
+**Events are the audit trail now.** Instead of querying state-change rows, subscribe to the lifecycle events that already fire on every meaningful transition: `order.placed`, `order.canceled`, `payment.completed`, `payment.voided`, `fulfillment.ready`, `fulfillment.fulfilled`, `fulfillment.canceled`, `fulfillment.resumed`, and the rest. If you need a persistent history, write it from a subscriber.
+
+**Gateway responses are no longer stored in your database.** `LogEntry` kept every gateway response as serialized YAML. For transaction forensics, use your payment provider's dashboard — `Payment#gateway_dashboard_payment_url` links straight to the transaction — or `Spree::PaymentSession`, which holds the gateway-side state for session-based providers.
+
+The `spree_state_changes` and `spree_log_entries` tables are **not dropped until 6.1**, so your existing rows survive the upgrade. If you want the history long-term, export it before upgrading to 6.1.
+
 ## Deprecated in 6.0, removed in 6.1
 
 Every rename keeps the legacy name working for one release with a deprecation warning. The notable ones:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@spree/docs",
-  "version": "0.1.147",
+  "version": "0.1.148",
   "description": "Spree Commerce developer documentation for AI agents and local reference",
   "type": "module",
   "license": "CC-BY-4.0",