@spree/docs 0.1.0

package/dist/developer/upgrades/4.1-to-4.2.md

@@ -0,0 +1,109 @@
+---
+title: 4.1 to 4.2
+section: upgrades
+order: 0
+description: This guide covers upgrading a 4.1 Spree application to Spree 4.2.
+---
+
+> **NOTE:** If you're on an older version than 4.1 please follow previous upgrade guides and perform those upgrades incrementally**, eg.
+> 
+> 1. [upgrade 3.7 to 4.0](3.7-to-4.0)
+> 2. [upgrade 4.0 to 4.1](4.0-to-4.1)
+
+## Update gems
+
+Run the following command to update your gems to 4.2:
+
+```bash
+bundle update
+```
+
+## Remove SpreeMultiCurrency optional
+
+If you used that gem in the past you need to remove it. Multi-Currency is now incorporated into Spree core and you cannot use that gem anymore.
+
+1. Remove `spree_multi_currency` from your `Gemfile`
+
+   ```bash
+   bundle remove spree_multi_currency
+   ```
+
+2. Remove these preferences from your Spree initializer `config/initializers/spree.rb`:
+   * `allow_currency_change`
+   * `show_currency_selector`
+   * `supported_currencies`
+3. Remove `//= require spree/frontend/spree_multi_currency` from `vendor/assets/javascripts/spree/frontend/all.js`
+4. Remove `//= require spree/backend/spree_multi_currency` from `vendor/assets/javascripts/spree/backend/all.js`
+
+## Optional Remove SpreeI18n config
+
+All international configuration is now kept on the `Store` model in the database rather than in initializer files.
+
+If you used `spree_i18n` gem before please remove any `SpreeI18n::Config`references from your `config/initializers/spree.rb` file.
+
+## Optional Add `deface` gem
+
+If you used [Deface overrides](../../advanced/deface_overrides_tutorial#organizing-overrides) you will need to include `deface` in your `Gemfile` as it was removed from Spree / Spree Auth Devise / Spree Gateway dependencies.
+
+```bash
+bundle add deface
+```
+
+## Fix RMA migration
+
+Please find a `add_stock_location_to_rma` migration in your `db/migrate` directory and change:
+
+```ruby
+class AddStockLocationToRma < ActiveRecord::Migration[4.2]
+```
+
+to
+
+```ruby
+class AddStockLocationToRMA < ActiveRecord::Migration[4.2]
+```
+
+## Install missing migrations
+
+```bash
+bin/rake spree:install:migrations
+```
+
+## Run migrations
+
+```bash
+bin/rails db:migrate
+```
+
+## Other things to remember
+
+### Replace `fast_json` with `jsonapi-serializer`
+
+Please follow [this guide to migrate your custom serializers](https://github.com/jsonapi-serializer/jsonapi-serializer#migrating-from-netflixfast_jsonapi).
+
+### Migrate select2 3.5 to 4
+
+Only if you've added new Admin Panel pages with Select2 dropdown - [this guide will help](https://select2.org/upgrading/migrating-from-35)
+
+### Make sure you've got up to date Spree templates Storefront
+
+If you're using Spree default Storefront `spree_frontend` gem make sure to update your templates, especially:
+
+* [app/views/spree/shared/_head.html.erb](https://github.com/spree/spree/blob/4-2-stable/frontend/app/views/spree/shared/_head.html.erb)
+* [app/views/spree/shared/_locale_and_currency.html.erb](https://github.com/spree/spree/blob/4-2-stable/frontend/app/views/spree/shared/_locale_and_currency.html.erb)
+* [app/views/spree/shared/_link_to_account.html.erb](https://github.com/spree/spree/blob/4-2-stable/frontend/app/views/spree/shared/_link_to_account.html.erb)
+* [app/views/spree/shared/_internationalization_options.html.erb](https://github.com/spree/spree/blob/main/frontend/app/views/spree/shared/_internationalization_options.html.erb)
+* [app/views/spree/shared/_locale_dropdown.html.erb](https://github.com/spree/spree/blob/4-2-stable/frontend/app/views/spree/shared/_locale_dropdown.html.erb)
+* [app/views/spree/shared/_currency_dropdown.html.erb](https://github.com/spree/spree/blob/4-2-stable/frontend/app/views/spree/shared/_currency_dropdown.html.erb)
+* [app/views/spree/shared/_mobile_navigation.html.erb](https://github.com/spree/spree/blob/4-2-stable/frontend/app/views/spree/shared/_mobile_navigation.html.erb)
+* [app/views/spree/shared/_mobile_internationalization_options.html.erb](https://github.com/spree/spree/blob/4-2-stable/frontend/app/views/spree/shared/_mobile_internationalization_options.html.erb)
+* [app/views/spree/shared/_nav_bar.html.erb](https://github.com/spree/spree/blob/4-2-stable/frontend/app/views/spree/shared/_nav_bar.html.erb)
+* [app/views/spree/shared/_line_item.html.erb](https://github.com/spree/spree/blob/4-2-stable/frontend/app/views/spree/shared/_line_item.html.erb)
+
+Or simply run `bin/rails g spree:frontend:copy_storefront`
+
+## Read the release notes
+
+For information about changes contained within this release, please read the [4.2.0 Release Notes](https://github.com/spree/spree/releases/tag/v4.2.0).
+
+## More info

package/dist/developer/upgrades/4.10-to-5.0.md

@@ -0,0 +1,129 @@
+---
+title: Upgrading to Spree 5.0
+description: This guide covers upgrading a Spree 4.10 application to Spree 5.0.
+---
+
+> **INFO:** Before proceeding to upgrade, please ensure you're at [Spree 4.10](/developer/upgrades/4.9-to-4.10)
+
+Spree 5.0 is a major upgrade that introduces many breaking changes. The major changes are:
+
+- Dropped support for Rails < 7.2
+- Dropped support for Spree Auth Devise gem (now using Devise gem directly via generator)
+- Completely new modern mobile-friendly Storefront (old customizations won't work)
+- Completely new Admin Dashboard (old customizations won't work)
+- Completely new native Stripe extension
+
+## Prerequisites
+
+Before upgrading, please ensure you have the following prerequisites:
+
+- Ruby 3.2 or later
+- Rails 7.2 - [Upgrade guide for Rails 7.2](https://guides.rubyonrails.org/upgrading_ruby_on_rails.html#upgrading-from-rails-7-1-to-rails-7-2)
+
+
+## Upgrade steps
+
+### 1. Remove old frontend/backend Spree gems
+
+```bash
+bundle remove spree_auth_devise spree_backend spree_frontend
+```
+
+> **WARNING:** Remove any code referencing `Spree::Backend`, `Spree::Fronted` or `Spree::Auth` from your application, especially from `config/initializers/spree.rb`.
+
+### 2. Update main Spree gem
+
+```bash
+bundle update spree
+```
+
+### 3. Install and run missing migrations
+
+```bash
+bin/rake spree:install:migrations && bin/rails db:migrate
+```
+
+### 4. Add new Spree gems
+
+```bash
+bundle add spree_storefront spree_admin spree_stripe
+```
+
+And run the following generators:
+
+```bash
+bin/rails g spree:storefront:install
+bin/rails g spree:admin:install
+bin/rails g spree_stripe:install
+```
+
+### 5. Migrate from Spree Auth Devise gem
+
+If you previously used the `spree_auth_devise` gem, you will need to run some commands to create User and connect it to Spree. We don't use the `spree_auth_devise` gem anymore to allow you more control over the authentication and access to all Devise options directly in your application.
+
+First, install Devise and run the Devise generator:
+
+```bash
+bundle add devise
+bin/rails g devise:install
+```
+
+Create `Spree::User` model:
+
+```bash
+mkdir -p app/models/spree && touch app/models/spree/user.rb
+```
+
+Add the following code to your `Spree::User` model:
+
+```ruby
+module Spree
+  class User < ApplicationRecord
+    devise :database_authenticatable # if you want to use the database_authenticatable feature
+    devise :recoverable # if you want to use the recoverable feature
+    devise :registerable # if you want to use the registerable feature
+    devise :confirmable # if you want to use the confirmable feature
+    devise :validatable # if you want to use the validatable feature
+
+    devise :rememberable, :trackable, :encryptable, encryptor: 'authlogic_sha512'
+
+    acts_as_paranoid
+  end
+end
+```
+
+In you `config/initializers/spree.rb` file, add the following code:
+
+```ruby
+Spree.user_class = "Spree::User"
+```
+
+Now run the new authentication generator to connect your `Spree::User` model to Spree:
+
+```bash
+bin/rails g spree:authentication:devise
+```
+
+And if you're using the default spree storefront, please run the following generator:
+
+```bash
+bin/rails g spree:storefront:devise
+```
+
+This will add devise routes and create controllers for the storefront.
+
+And that's it! You can now login to the admin panel and storefront using your existing users.
+
+### 6. Migrate data to the new format
+
+In Spree 5 we changed a bit of the data in some models so you will need to run these commands to fix it:
+
+#### Taxons
+
+```ruby
+Spree::Taxon.all.each { |t| t.set_pretty_name; t.save }
+```
+
+## Read the release notes
+
+For information about changes contained within this release, please read the [Spree 5.0 Release Notes.](https://github.com/orgs/spree/discussions/12604)

package/dist/developer/upgrades/4.2-to-4.3.md

@@ -0,0 +1,100 @@
+---
+title: 4.2 to 4.3
+section: upgrades
+order: 0
+hidden: true
+description: This guide covers upgrading a 4.2 Spree application to Spree 4.3.
+---
+
+> **NOTE:** If you're on an older version than 4.1 please follow previous upgrade guides and perform those upgrades incrementally**, eg.
+> 
+> 1. [upgrade 3.7 to 4.0](3.7-to-4.0)
+> 2. [upgrade 4.0 to 4.1](4.0-to-4.1)
+> 3. [upgrade 4.1 to 4.2](4.1-to-4.2)
+
+## Update Gemfile
+
+Since Spree 4.3 `spree` gem doesn't include `spree_emails`, `spree_backend` and `spree_frontend` gems. It only consists of Spree Core and Spree API.
+
+You need to add them to your Gemfile if you want to use them.
+
+```bash
+bundle add spree_emails spree_backend spree_frontend
+```
+
+## Remove gems merged into Spree Core
+
+These gems were merged into Spree Core in version 4.3. All of their functionality is now included in the `spree` gem so you can remove them.
+
+### Optional Remove SpreeMultiDomain
+
+If you used that gem in the past you need to remove it. Multi-Store is now incorporated into Spree core and you cannot use that gem anymore.
+
+1. Remove `spree_multi_domain` from your `Gemfile`
+
+    ```bash
+    bundle remove spree_multi_domain
+    ```
+
+2. Remove `//= require spree/frontend/spree_multi_domain` from `vendor/assets/javascripts/spree/frontend/all.js`
+3. Remove `//= require spree/backend/spree_multi_domain` from `vendor/assets/javascripts/spree/backend/all.js`
+
+### Optional Remove Spree Editor
+
+Spree 4.3 includes TinyMCE 5 editor built-in. It's not recommended to use `spree_editor` gem anymore.
+
+```bash
+bundle remove spree_editor
+```
+
+### Optional Remove Spree Static Content
+
+Spree 4.3 includes a built-in CMS. It's not recommended to use `spree_static_content`
+
+```bash
+bundle remove spree_static_content
+```
+
+## Install missing migrations
+
+```bash
+rake railties:install:migrations
+```
+
+## Run migrations
+
+```bash
+bin/rails db:migrate
+```
+
+## Additional fixes and hints
+
+### Upgrade Sprockets to v4
+
+In your project create  `app/assets/config/manifest.jss` file with contents:
+
+```ruby
+//= link_tree ../images
+//= link_tree ../javascripts
+//= link_directory ../stylesheets .css
+```
+
+More [on this topic](https://github.com/rails/sprockets/blob/main/UPGRADING.md#manifestjs).
+
+### Admin Panel fix
+
+If you've developed custom features for your Admin Panel, please replace any occurrences of
+
+```ruby
+render partial: 'spree/shared/error_messages'
+```
+
+to
+
+```ruby
+render partial: 'spree/admin/shared/error_messages'
+```
+
+## Read the release notes
+
+For information about changes contained within this release, please read the [Release notes](https://github.com/spree/spree/releases/v4.3.0).

package/dist/developer/upgrades/4.3-to-4.4.md

@@ -0,0 +1,125 @@
+---
+title: 4.3 to 4.4
+description: This guide covers upgrading a 4.3 Spree application to Spree 4.4.
+---
+
+> **NOTE:** If you're on an older version than 4.3 please follow previous upgrade guides and perform those upgrades incrementally, eg.
+> 
+> 1. [upgrade 4.0 to 4.1](4.0-to-4.1)
+> 2. [upgrade 4.1 to 4.2](4.1-to-4.2)
+> 3. [upgrade 4.2 to 4.3](4.2-to-4.3)
+
+## Update Gems
+
+Run the following command to update your gems to 4.4:
+
+```bash
+bundle update
+```
+
+to install the new gems.
+
+## Remove gems merged into Spree Core
+
+These gems were merged into Spree Core in version 4.4. All of their functionality is now included in the `spree` gem so you can remove them.
+
+### (Optional) Remove Spree Digital
+
+If you used that gem in the past you need to remove it. Digital products are now incorporated into Spree core and you cannot use that gem anymore.
+
+1. Remove `spree_digital` from your `Gemfile`
+
+### (Optional) Remove Spree Wishlist
+
+If you used that gem in the past you need to remove it. Wishlists are now incorporated into Spree core and you cannot use that gem anymore.
+
+1. Remove `spree_wishlist` from your `Gemfile`
+2. (Optional) Remove `//= require spree/frontend/spree_wishlist` from `vendor/assets/javascripts/spree/frontend/all.js`
+3. (Optional) Remove `*= require spree/frontend/spree_wishlist` from `vendor/assets/stylesheets/spree/frontend/all.css`
+
+## Update gems
+
+```bash
+bundle update
+```
+
+## Install missing migrations
+
+```bash
+bin/rake spree:install:migrations
+```
+
+## Run migrations
+
+```bash
+bin/rails db:migrate
+```
+
+## Run install generators
+
+This will copy some files from `spree_backend` to your application.
+
+```bash
+bin/rails g spree:backend:install
+```
+
+If you're using `spree_frontend` you need to run the frontend install generator as well:
+
+```bash
+bin/rails g spree:frontend:install
+```
+
+## Additional fixes and hints
+
+### Make sure that Node is available in your cloud environment
+
+On Heroku, you need to add the node buildpack - [https://devcenter.heroku.com/articles/buildpacks#using-multiple-buildpacks](https://devcenter.heroku.com/articles/buildpacks#using-multiple-buildpacks)
+
+### Add Spree ActiveJob queues to your Sidekiq config
+
+Spree uses ActiveJob for processing long running operations to not interrupt your web server performance.
+
+If you're using [Sidekiq](https://github.com/mperham/sidekiq) you need to update your `config/sidekiq.yml` file and 2 new queues:
+
+* `spree_stock_location_stock_items`
+* `spree_webhooks`
+
+### Disabling webhooks
+
+Spree 4.4 introduces webhook events for most of the Spree resources (Products, Orders, Customers, etc). If you wish to disable this globally you can set the environment variable:
+
+```bash
+DISABLE_SPREE_WEBHOOKS=true
+```
+
+If you would like to disable firing webhooks for certain elements of your application you can wrap these methods in a block:
+
+```ruby
+Spree::Webhooks.disable_webhooks do
+  ... run your code here ...
+end
+```
+
+Webhooks do not fire on touch events. Webhooks also do not do anything until there is a first webhook subscriber created which can be done in the Admin Dashboard or via Platform API.
+
+### Update Spree Dependencies that was renamed
+
+Please change in your codebase:
+
+```ruby
+Spree::Dependencies.account_update_address_service
+```
+
+to
+
+```ruby
+Spree::Dependencies.address_update_service
+```
+
+## Read the release notes
+
+For information about changes contained within this release, please read the [CHANGELOG](https://github.com/spree/spree/releases/tag/v4.4.0).
+
+## More info
+
+If you have any questions or suggestions feel free to [contact us via email](https://spreecommerce.org/contact) or through [Spree slack channels](http://slack.spreecommerce.org/)

package/dist/developer/upgrades/4.4-to-4.5.md

@@ -0,0 +1,94 @@
+---
+title: 4.4 to 4.5
+description: This guide covers upgrading a 4.4 Spree application to Spree 4.5
+---
+
+> **WARNING:** We recommend [upgrading straight to 4.8](4.x-to-4.8), as we improved how we handle translations in 4.8.
+> This also means easier database migration, especially if you have a big product catalog.
+
+> **NOTE:** If you're on an older version than 4.4 please follow previous upgrade guides and perform those upgrades incrementally, eg.
+> 
+> 1. [upgrade 4.1 to 4.2](4.1-to-4.2)
+> 2. [upgrade 4.2 to 4.3](4.2-to-4.3)
+> 3. [upgrade 4.3 to 4.4](4.3-to-4.4)
+
+## Upgrade Rails
+
+> **WARNING:** Rails 6.0 is no longer supported - if you haven’t already, you’ll need to upgrade to **Rails 6.1 or 7.x**.
+
+The effort to upgrade to Rails 6.1 is relatively low and brings a lot of improvements around ActiveStorage and handling of CDNs. See the Rails docs [for upgrading from 6.0 to 6.1](https://edgeguides.rubyonrails.org/upgrading_ruby_on_rails.html#upgrading-from-rails-6-0-to-rails-6-1), and for [upgrading from 6.1 to 7.0](https://edgeguides.rubyonrails.org/upgrading_ruby_on_rails.html#upgrading-from-rails-6-1-to-rails-7-0).
+
+> **NOTE:** If using Rails 7, you will need to [install libvips](https://www.libvips.org/install.html) on your cloud environment, as Rails 7 uses vips as its default variant processor. You can still use imagemagick, but you’ll need to manually set it in your [Rails config](https://edgeapi.rubyonrails.org/classes/ActiveStorage/Variant.html).
+
+### Rails 7 specific changes
+
+#### Update Spree Config
+
+If you're upgrading your app to Rails 7, you'll need to make a slight update to your spree config initializer. In `config/initializers/spree.rb`, wrap the `Spree.config` block in a `Rails.application.config.after_initialize` block, like so:
+
+```ruby
+Rails.application.config.after_initialize do
+  Spree.config do |config|
+    # config settings initialized here
+  end
+end
+```
+
+If you don't perform this update to the code, you may expect to get the following error:
+
+```ruby
+/lib/spree/core/preferences/store.rb:96:in `should_persist?': 
+uninitialized constant Spree::Preference (NameError)
+```
+
+#### Update other initializers
+
+Just like with `Spree::Config`, you may need to [update other intializers in your application, that use autoloadable constants](https://rubyonrails.org/2021/9/3/autoloading-in-rails-7-get-ready).
+
+For example, if you use `spree_auth_devise`, you'll need to update `config/initializers/devise.rb` and wrap the configuration in `Rails.application.config.after_initialize` block:
+
+```ruby
+Rails.application.config.after_initialize do
+  if defined?(Spree::Auth)
+    Spree::Auth::Config.signout_after_password_change = false
+  end
+end
+```
+
+## Update gems
+
+Run the following command to update your gems to 4.4:
+
+```bash
+bundle update
+```
+
+Legacy REST API v1 was extracted from the spree gem in 4.4. If your application depends on the Spree v1 API, you'll have to include it as a gem in your `Gemfile`:
+
+```bash
+bundle add spree_api_v1
+```
+
+## Install missing migrations
+
+```bash
+bin/rake spree:install:migrations
+```
+
+## Run migrations
+
+```bash
+bin/rails db:migrate
+```
+
+## Run Additional Commands for Frontend
+
+If using [Spree Frontend](https://github.com/spree/spree_rails_frontend), run the following additional commands to get everything set up correctly with the updated gems:
+
+```bash
+bin/rails g spree:frontend:install
+```
+
+## Read the release notes
+
+For information about changes contained within this release, please read the [Spree 4.5.0 Release Notes](https://github.com/spree/spree/releases/tag/v4.5.0).

package/dist/developer/upgrades/4.5-to-4.6.md

@@ -0,0 +1,119 @@
+---
+title: 4.5 to 4.6
+description: This guide covers upgrading a 4.5 Spree application to Spree 4.6.
+---
+
+> **WARNING:** We recommend [upgrading straight to 4.8](4.x-to-4.8), as we improved how we handle translations in 4.8.
+> This also means easier database migration, especially if you have a big product catalog.
+
+> **NOTE:** If you're on an older version than 4.5 please follow previous upgrade guides and perform those upgrades incrementally, e.g.
+> 
+> 1. [upgrade 4.2 to 4.3](4.2-to-4.3)
+> 2. [upgrade 4.3 to 4.4](4.3-to-4.4)
+> 3. [upgrade 4.4 to 4.5](4.4-to-4.5)
+
+## Update gems
+
+Run the following command to update your gems to 4.6:
+
+```bash
+bundle update
+```
+
+## (Optional) Remove spree_globalize
+
+If your application used the spree_globalize extension, you can remove it from your Gemfile, as translations are now supported out-of-the-box with the [Mobility](https://github.com/shioyama/mobility) gem.
+
+We've configured Mobility to use [a strategy that uses a separate table to store translations](https://dejimata.com/2017/3/3/translating-with-mobility#strategy-2), just like how spree_globalize did. This means, you won't need to make any changes to the database structure or migrate data.
+
+During the upgrade process, you may need to review your custom queries that rely on translations, as there are minor differences in how Mobility handles them. Spree 4.6 includes a few [built-in concerns](/developer/core-concepts/translations#resource-translations-implementation) to make it easier to work with translatable models.
+
+Run the following command to remove spree_globalize from your Gemfile:
+
+```bash
+bundle remove spree_globalize
+```
+
+## Install missing migrations
+
+```bash
+bin/rake spree:install:migrations
+```
+
+## Run migrations
+
+```bash
+bin/rails db:migrate
+```
+
+> **NOTE:** If you didn't use `spree_globalize` before, this will install migrations that move some columns from `spree_products`, `spree_taxons`, to dedicated translation tables such as `spree_products_translations`, `spree_taxons_translations` etc.
+> 
+> If you're using raw SQL queries (either in the application code, or running in external tools), you may need to review the new structure and update your queries accordingly.
+
+### Run install generators
+
+This will copy some files from `spree_backend` to your application.
+
+```bash
+bin/rails g spree:backend:install
+```
+
+If you're using `spree_frontend` you need to run the frontend install generator as well:
+
+```bash
+bin/rails g spree:frontend:install
+```
+
+## Additional fixes and hints
+
+### Update migrations for translation tables with additional columns
+
+If you want to translate more fields in [translated resources](/developer/core-concepts/translations#resource-translations), you have to alter copied migrations or add new ones.
+We're using the [Spree::TranslationMigrations](https://github.com/spree/spree/blob/main/core/lib/spree/translation_migrations.rb) to help with migrating data.
+
+### Add or update the behavior of the translated model
+
+Each translated resource has a corresponding `Translation` model, see [here](https://github.com/spree/spree/blob/v4.6.5/core/app/models/spree/product.rb#L44) for reference.
+If you want to add some more behavior to the translation, you need to do it within the `Translation.class_eval` block.
+
+If you overwrote Spree models in your application, you have to define this block yourself. Apart from that, please include these modules: 
+- `Spree::TranslatableResource` - required for all translated models
+- `Spree::TranslatableResourceSlug` - required for translated models with slugs/permalinks
+
+[Read more](/developer/core-concepts/translations#resource-translations-implementation) how Spree handles resource translations.
+
+### Generating slugs with `friendly_id`
+
+Generating slugs/permalinks in `Spree::Product` and `Spree::Taxon` models is now based on the translated name. If you use the `history` plugin, [read on how to use it](https://github.com/shioyama/friendly_id-mobility?tab=readme-ov-file#slug-history) with the `mobility` gem.
+
+### Resource translations and encryption
+
+Currently, it's not possible to translate encrypted data. If you're already encrypting data that Spree translates, you need to remove that functionality.
+
+### Full text search with pg_search scopes
+
+If you use the [pg_search](https://github.com/Casecommons/pg_search) for the full text search in [translated resources](/developer/core-concepts/translations#resource-translations), you need to move your scopes to the translated model, eg. from the `Spree::Product` to the `Spree::Product::Translation`. 
+
+If you still want to have the original scope, you need to rewrite it, from:
+
+```ruby
+pg_search_scope :search_by_name, against: :name
+```
+
+to:
+
+```ruby
+self::Translation.class_eval do
+  include PgSearch::Model
+  pg_search_scope :search_by_name, against: :name
+end
+
+scope :search_by_name, lambda { |query|
+  product_ids = Spree::Product::Translation.search_by_name(query).pluck(:spree_product_id)
+  where(id: product_ids)
+}
+```
+
+## Read the release notes
+
+For information about changes contained within this release, please read the [Spree 4.6.0 Release Notes](https://github.com/spree/spree/releases/tag/v4.6.0).