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

Bump decidim from v0.29.2 to v0.30.0.rc1 #142

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

andreslucena
Copy link
Member

This PR updates to the last release candidate version, released yesterday

Mind that there are some changes that need to be handled server-side: https://github.com/decidim/decidim/releases/tag/v0.30.0.rc1

I opened another PR but found a mini bug on the migrations that we fixed on decidim/decidim#14125 and I'm applying manually here so we can skip doing the rc2 just for this tiny bug 😄

Mind that I had to manually change the `db/schema.rb` file, as the
migrations for this application are broken: in 2017 we did a lot of
manual migrations that doesn't exist upstream (in decidim/decidim) and
that generates a problem locally and in testing where we can't run the
`db:migrate` task in a new database, but we need to do the
`db:schema:load` or `db:test:prepare` that loads the schema from the
schema.rb file instead of running each of the migrations.

Some examples of these files are:

- db/migrate/20170606113833_add_index_to_accountability_results_on_external_id.decidim_accountability.rb
- db/migrate/20170128100053_allow_erased_users.rb
- db/migrate/20170405084212_fix_email_uniqueness_index.rb
- db/migrate/20170125130555_remove_attachments_table.rb
@andreslucena andreslucena force-pushed the deps/decidim/0.30.0.rc1-2 branch from 890fe91 to c483adb Compare February 19, 2025 10:47
Copy link
Contributor

@alecslupu alecslupu left a comment

Choose a reason for hiding this comment

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

LGTM.
I see a lot of migrations that have been changed ( ~ 600+ ) but most of them have a small change caused by upgrade from rails 6.1 to 7.0

image

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.

3 participants