@spree/docs 0.1.35 → 0.1.37

package/dist/api-reference/admin-api/introduction.md

@@ -3,6 +3,9 @@ title: "Admin API"
 sidebarTitle: "Introduction"
 ---
 
+import { Since } from '/snippets/since.mdx';
+
+
 > **WARNING:** **Developer Preview.** The Admin API is in active development and may change between major versions.
 
 The Admin API is a REST API for managing a Spree stores programmatically — products, orders, customers, fulfillments, payments, and more. It is intended for backend integrations, custom admin tooling, and automation.

package/dist/api-reference/store-api/introduction.md

@@ -3,6 +3,9 @@ title: "Store API"
 sidebarTitle: "Introduction"
 ---
 
+import { Since } from '/snippets/since.mdx';
+
+
 This API reference includes Spree Store APIs, which are REST APIs exposed by the Spree application. They are used to create a storefront for your commerce store, such as a website, point of sale or a commerce mobile app.
 
 All API Routes are prefixed with `/api/v3/store`. So, during development, the API Routes will be available under the path `http://localhost:3000/api/v3/store`. For production, replace `http://localhost:3000` with your Spree application URL.

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

@@ -3,6 +3,9 @@ title: Events
 description: Learn how Spree's event system works and how to subscribe to events.
 ---
 
+import { Since } from '/snippets/since.mdx';
+
+
 ## Overview
 
 Spree includes a powerful event system that allows you to react to various actions happening in your store. When something happens (an order is completed, a product is created, etc.), Spree publishes an event that your code can subscribe to and handle.

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

@@ -3,6 +3,9 @@ title: Markets
 description: Multi-region commerce with Markets — bundle geography, currency, and locale into distinct selling regions within a single store.
 ---
 
+import { Since } from '/snippets/since.mdx';
+
+
 ## Overview
 
 Markets let you segment a single [Store](stores.md) into distinct geographic regions, each with its own currency, locale, and set of countries. For example, an international store might define:

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

@@ -4,6 +4,8 @@ sidebarTitle: "Media"
 description: Product media (images, videos), named variants, focal points, and how media is served via the Store API
 ---
 
+import { Since } from '/snippets/since.mdx';
+
 ## Overview
 
 Spree handles uploads, processing, and delivery for product media. Images are automatically converted to WebP format and preprocessed into multiple sizes for optimal performance.
@@ -22,7 +24,7 @@ Each media item has a `media_type` field that defaults to `image`. The `variant_
 
 > **NOTE:** `Spree::Image` is a backward-compatible subclass of `Spree::Asset` that sets `media_type` to `image`. New code should use `Spree::Asset` directly.
 
-### Named Variant Sizes
+### Named Variant Sizes 
 
 When an image is uploaded, Spree automatically generates optimized versions in the background:
 

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

@@ -3,6 +3,8 @@ title: Pricing
 description: Prices, Price Lists, Price Rules, and the Pricing Context — Spree's flexible pricing engine for regional, wholesale, volume, and market-based pricing.
 ---
 
+import { Since } from '/snippets/since.mdx';
+
 ## Overview
 
 Spree's pricing system supports both simple single-currency pricing and advanced multi-currency, rule-based pricing through Price Lists. Every [Variant](products.md#variants) can have multiple prices — a base price per currency, plus additional prices from Price Lists that apply conditionally based on rules like geography, customer segment, or quantity.
@@ -51,7 +53,7 @@ curl 'https://api.mystore.com/api/v3/store/products/spree-tote?expand=variants'
 ```
 
 
-## Price Lists
+## Price Lists  
 
 Price Lists allow you to create different pricing strategies based on various conditions. This enables advanced pricing scenarios like:
 
@@ -84,7 +86,7 @@ If no applicable Price List is found, the base price is used.
 | `match_policy` | How rules are evaluated: `all` (every rule must match) or `any` (at least one) |
 | `position` | Priority order (lower numbers = higher priority) |
 
-## Price Rules
+## Price Rules 
 
 Price Rules define conditions that must be met for a Price List to apply. Spree includes five built-in rule types:
 
@@ -96,7 +98,7 @@ Price Rules define conditions that must be met for a Price List to apply. Spree
 | **Customer Group Rule** | Matches members of customer groups | Loyalty tiers, membership pricing |
 | **Volume Rule** | Matches based on quantity purchased | Bulk discounts, tiered pricing |
 
-### Market Rule
+### Market Rule 
 
 The recommended approach for regional pricing when using Markets. Applies the Price List when the customer is in one of the specified markets.
 
@@ -126,7 +128,7 @@ Applies based on quantity purchased. Supports `min_quantity` and `max_quantity`
 
 > **INFO:** Custom Price Rules can be created for specialized pricing logic. See the [Customization Quickstart](../customization/quickstart.md) for details.
 
-## Pricing Context
+## Pricing Context 
 
 When resolving prices, Spree considers the full context of the request:
 
@@ -155,7 +157,7 @@ Price Lists are managed in the Admin Panel under **Products → Price Lists**, o
 
 Each Price List contains prices for specific variants and currencies. Products can be added to a Price List, and individual variant prices set within it.
 
-## Price History (EU Omnibus Directive)
+## Price History (EU Omnibus Directive) 
 
 Spree automatically records price changes for EU Omnibus Directive compliance. When a product goes on sale, EU regulations require displaying the lowest price in the preceding 30 days alongside the discounted price.
 

package/dist/developer/core-concepts/search-filtering.md

@@ -3,6 +3,8 @@ title: Search & Filtering
 description: "Search, filter, and sort products and other resources via the Store API"
 ---
 
+import { Since } from '/snippets/since.mdx';
+
 ## Overview
 
 Spree provides powerful search, filtering, and sorting capabilities for products and other resources. The Store API supports:
@@ -225,7 +227,7 @@ curl 'https://api.mystore.com/api/v3/store/products?page=1&limit=24' \
 
 See [Querying](../../api-reference/store-api/querying.md) for the full list of filtering, sorting, and pagination options.
 
-## Search Providers
+## Search Providers 
 
 Spree uses a pluggable search provider architecture. The default provider uses SQL (ILIKE + Ransack). For production catalogs with 1,000+ products, we recommend switching to [Meilisearch](../../integrations/search/meilisearch.md) for typo tolerance, relevance ranking, and faster faceted search.
 

package/dist/developer/core-concepts/store-credits-gift-cards.md

@@ -3,6 +3,9 @@ title: Store Credits & Gift Cards
 description: Stored value mechanisms for refunds, loyalty rewards, and gifting
 ---
 
+import { Since } from '/snippets/since.mdx';
+
+
 ## Overview
 
 Spree provides two stored value mechanisms that customers can use at checkout:

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

@@ -3,6 +3,9 @@ title: Webhooks
 description: Send real-time HTTP notifications to external services when events occur in your store.
 ---
 
+import { Since } from '/snippets/since.mdx';
+
+
 ## Overview
 
 Webhooks allow your Spree store to send real-time HTTP POST notifications to external services when events occur. When an order is completed, a product is updated, or inventory changes, Spree can automatically notify your CRM, fulfillment service, analytics platform, or any other system.

package/package.json

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