Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v2.8.2 #3117

Merged
merged 4 commits into from
Feb 25, 2019
Merged

v2.8.2 #3117

merged 4 commits into from
Feb 25, 2019

Conversation

kennyadsl
Copy link
Member

@kennyadsl kennyadsl commented Feb 21, 2019

Description

This PR adds some fixes on Solidus v2.8 that are already present in master and could help users that still have to update Solidus to this version.

A summary of changes:

  1. Allow setting weight and dimensions on products without variants
  2. Remove destructive actions from one migrations related to store credit reasons: The reason is well explained into the PR, anyway the plan in to restore those destructive actions in a future version of Solidus, probably 2.9. If users already run this migration, it should be safe to run the new one on 2.9, since this scenario has been taken into account: Add migration to drop table/column from 20180710170104 #3114
  3. Fix some errors while running the migration that removes code columns from spree_promotions: While upgrading a store started many years ago, we noticed that there were cases where database has inconsistent data. This fix should simplify the upgrade.

They are meant to be released with a new patch version v2.8.2.

Checklist:

seand7565 and others added 4 commits February 21, 2019 09:57
spree_promotions table used to be named spree_activators in legacy
spree versions. This table was used by many models with STI via the type
column. After it has been renamed into spree_promotions, having this
type field does not make sense anymore.
Promotions could have code nil, but also an empty string. This commit
takes into account this scenario since we don't want to take any action
on promotions with code nil or empty.
Removing tables and renaming columns are destructive actions as they change the
DB schema in a way that is likely to be not compatible with previous code.

This is especially dangerous when deploying multi-instance applications as
migrations can run before all instances code is synced. When this happens,
these instances may experience severe downtime due to high error rates.

So destructive changes should be done in subsequent deploys: first add the new
table and columns, then later remove the stale ones.

Table `spree_store_credit_update_reasons` and its column `update_reason_id`
will need to be removed in a future release of Solidus.
Copy link
Contributor

@jacobherrington jacobherrington left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am good with this 👍

Copy link
Member

@tvdeyen tvdeyen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 Thanks

@kennyadsl kennyadsl merged commit 906bc40 into solidusio:v2.8 Feb 25, 2019
@kennyadsl kennyadsl deleted the kennyadsl/v2.8.2 branch February 25, 2019 10:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants