Add more guardrails to enforce 2.x upgrade before 3.x

Created on 11 November 2023, over 1 year ago

Updated 3 September 2024, 6 months ago

For sites that started on a beta or earlier release of 2.x, it is necessary to upgrade to the latest version of 2.x BEFORE upgrading to 3.x.

While this has been noted in several places, e.g. the release notes and the module home page, it still gets overlooked at times.

We should remove the 2.x database update hooks from 3.x and use hook_update_last_removed to ensure that those updates are applied.

📌 Task

Status

Fixed

Version

3.0

Component

Code

Created by

🇺🇸United States TomTech

Live updates comments and jobs are added and updated live.

Comments & Activities

c158bcc8 committed on 3.0.x

Issue #3400994: Add more guardrails to enforce 2.x upgrade before 3.x

Status changed to Fixed over 1 year ago3:48pm 11 November 2023
Comment over 1 year ago →
🇺🇸United States TomTech
Comment about 1 year ago →
System Message
Automatically closed - issue fixed for 2 weeks with no activity.
Status changed to Fixed 6 months ago3:49pm 3 September 2024
Comment 6 months ago →
🇺🇸United States TomTech

Production build 0.71.5 2024