Lunar 1.5.0

​

Framework support

​

High impact changes

​

Nested set package replaced

​

Order line purchasable morph is now nullable

​

Discount conditions honored by BuyXGetY

​

Stripe amount conversion

​

Discounts

• Coupon codes now apply immediately on stores that also have an always-on discount. The memoized discount set was reused across carts within a request, which excluded coupon discounts and left the total unchanged until the page was reloaded.
• Re-creating a draft order for the same cart no longer consumes another use of its discounts. A card decline followed by a retry previously exhausted the coupon and re-priced the same order without it. Carts now track their own consumed discounts through consumedDiscountIds().
• BuyXGetY supports a specific product variant as an automatically added reward. This previously raised a fatal error during cart calculation, taking down the basket rather than just checkout.
• A multi-quantity BuyXGetY reward is added as one line with that quantity, rather than one line per item.
• Automatically added reward lines are stored using Lunar’s morph map, so their purchasable_type matches every other line holding the same purchasable.
• Automatic rewards only select items that can be fulfilled, so an out-of-stock reward is skipped rather than raising an error.
• Collection breadcrumbs are shown in the admin panel’s discount selection lists, making collections with the same name distinguishable.
• Discount usage lookups are memoized per cart instance, cutting repeated draft-order queries on every calculate.

​

Carts and orders

• Switching the session currency now reprices the cart. CartSession::setCurrency() updated the cart’s currency_id but left the loaded relationships in place, so the next calculate priced every line in the previous currency. See Carts.
• Shipping modifiers can safely calculate the cart. A modifier that did so previously re-entered the modifier pipeline and exhausted the stack, which surfaced only once a shipping address with a selected option was present.
• Order creation no longer duplicates addresses of the same type. Existing addresses are matched on type alone, so rebuilding a draft order with a changed address updates it in place.
• Cart::lines() and Order::lines() order by id, and ProductVariant::values() orders by position. These relationships previously left row order to the database engine, which is stable on MySQL but not on PostgreSQL, where it could change a cart’s fingerprint after an unrelated update.
• Order lines for digital products appear on the generated invoice PDF. The template iterated physical lines only, silently omitting non-shippable products and services.

​

Tax

• State tax zones are scoped to the address country. A state zone previously matched any address with a matching state code or name in any country, so a shopper in Western Australia could be charged Washington State sales tax. See Taxation.
• SystemTaxDriver resolves the default tax zone through TaxZone::getDefault(), removing duplicate queries during cart calculation.

​

Shipping

• Weight tiers on the ship-by driver are evaluated in the shipping method’s configured weight_unit, defaulting to kg. Each cart line’s weight is converted from its own unit first, so a cart mixing grams and kilograms totals correctly. Methods that set a unit other than kg need their tier thresholds re-entered in that unit. See Table Rate Shipping.
• The admin tier form shows the configured unit and rejects decimal weight tiers, instead of silently truncating them.
• Shipping Zone create and update no longer fail validation with “The selected countries is invalid” when limiting a zone to specific countries or states.
• The Shipping permission is translated in the admin panel.

​

Admin panel

• A new Lunar\Admin\Events\ProductVariantInventoryUpdated event is dispatched when stock is saved on the product or variant inventory pages, bringing inventory changes in line with the panel’s other resource events. See Extending the Admin Panel.
• Attribute default_value is exposed in the admin panel and applied when creating records.
• Media custom properties are no longer dropped on create or edit. Keys contributed through a RelationManagerExtension are persisted, and keys the edit form does not render survive a save.
• Customers can be deleted individually, rather than only through the bulk action.
• Product option mapping no longer shows the first variant’s SKU against unmatched option permutations, and newly added permutations save correctly, inheriting their tax class and pricing from the oldest sibling variant.
• The Unit Quantity field on product variants enforces a minimum of 1, preventing a division by zero when the item is added to a cart.
• Boolean order metadata is displayed as Yes or No rather than a raw value.
• Product variant widget labels are translated.
• Whitespace is trimmed from panel form inputs.

​

Developer experience

• A Laravel Boost skill ships with the core package, installable with php artisan boost:add-skill lunarphp/lunar. It orients an AI assistant in a Lunar project and points it at current documentation. See AI Development.
• Date parameters on the channel and customer group scoping and scheduling traits accept DateTimeInterface, so applications using Date::use(CarbonImmutable::class) no longer hit a TypeError during cart and discount calculation.
• HasDefaultRecord::getDefault() is annotated as nullable, matching what it returns when no record is flagged as the default.
• The $formatterStyle parameter on DefaultPriceFormatter is typed int, matching the NumberFormatter constants passed to it.
• Route facade imports are fixed in the Opayo and PayPal route files.

​

Upgrading

composer update lunarphp/lunar
php artisan migrate
php artisan optimize:clear

​

Thanks