Bump solidus from master to 3.0.0

[dependabot-preview]

Bumps solidus from master to 3.0.0. This release includes the previously tagged commit.

Release notes

Sourced from solidus's releases.

v3.0.0

🎉 Solidus 3.0 is out!

This version is almost identical to the last 2.11.x version with the only difference that we removed all the code deprecated. Here's a list of things to take into account while upgrading.

Major Changes

Removal of all code deprecated during the 2.x series

The main change in this major version is the removal of all deprecated code that we introduced during the 2.x series. This means that if any code that was deprecated is still being used, the application will break. Following the deprecation messages in the application logs, it should be quite easy to spot what code needs to be changed.

The main things that could break a Solidus application are:

Paranoia gem has been replaced by Discard gem

All references to methods added to models by Paranoia will raise a NoMethodError exception now. Some of those methods are:

• paranoia_destroy
• paranoia_delete
• with_deleted
• only_deleted
• really_destroy!
• after_real_destroy

Pull Requests:

• Discard Paranoia #3488 (cedum)

Removed core support to first_name and last_name in Spree::Address

In Solidus v2.11, we added a name attribute to Spree::Address, which is being populated combining first_name and last_name values every time a new address is added to the system. We also provided a rake task to update all existing records in order to get applications ready for Solidus 3.0.

With this major version, name is the only supported attributes. first_name and last_name fields are already in the database so if needed, a store can revert this change by implementing its own logic.

See 3234 for the rationale behind this change.

Pull Requests:

• Move Spree::Address#name attribute to the db #3908 (filippoliverani)
• Remove deprecated name-related Address fields #3820 (filippoliverani)

All the other deprecations removal

... (truncated)

Changelog

Sourced from solidus's changelog.

Solidus 3.0.0 (v3.0, 2021-04-20)

Major Changes

Removal of all code deprecated during the 2.x series

The main change in this major version is the removal of all deprecated code that we introduced during the 2.x series. This means that if any code that was deprecated is still being used, the application will break. Following the deprecation messages in the application logs, it should be quite easy to spot what code needs to be changed.

The main things that could break a Solidus application are:

Paranoia gem has been replaced by Discard gem

All references to methods added to models by Paranoia will raise a NoMethodError exception now. Some of those methods are:

• paranoia_destroy
• paranoia_delete
• with_deleted
• only_deleted
• really_destroy!
• after_real_destroy

Pull Requests:

• Discard Paranoia #3488 (cedum)

Removed core support to first_name and last_name in Spree::Address

In Solidus v2.11, we added a name attribute to Spree::Address, which is being populated combining first_name and last_name values every time a new address is added to the system. We also provided a rake tasks to update all existing records in order to get applications ready for Solidus 3.0.

With this major version, name is the only supported attributes. first_name and last_name fields are already in the database so if needed, a store can revert this change implementing their own logic.

See 3234 for the rationale behind this change.

Pull Requests:

• Move Spree::Address#name attribute to the db #3908 (filippoliverani)
• Remove deprecated name-related Address fields #3820 (filippoliverani)

All the other deprecations removal

For a complete reference to rest of the code removed, these PRs can be taken as reference:

• Remove deprecated attachment_partial_name #3974 (kennyadsl)

... (truncated)

Commits

• a731a1a Bump Solidus to 3.0.0
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)