Upgrade path D9->D10

Created on 21 June 2023, over 1 year ago
Updated 5 August 2023, over 1 year ago

Problem/Motivation

Since 3.x only supports D9 and 4.x only supports D10, what is your suggested upgrade path on upgrading a D9 site that uses this module?

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

✨ Feature request
Status

Closed: won't fix

Version

4.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States kwfinken Lansing, MI

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @kwfinken
  • Status changed to Closed: works as designed over 1 year ago
  • πŸ‡¦πŸ‡ΊAustralia dpi Perth, Australia

    See project page.

    Change your contraints to ^3 || ^4

  • Status changed to Active over 1 year ago
  • πŸ‡ΊπŸ‡ΈUnited States kwfinken Lansing, MI

    What would be nice is if the 4.x supported D9, change it's info.yml and composer.json to allow D9 and then we could upgrade the module, verify it and then separately upgrade to D10. Upgrading 1 thing at a time is best practices. This is a simple change allowing the newest version of the module to work with D9.

  • Status changed to Closed: won't fix over 1 year ago
  • πŸ‡¦πŸ‡ΊAustralia dpi Perth, Australia

    Some projects choose to cut off major versions, its a matter of maintenance preference.

    I disagree that it is best practice.

    The upgrade process has been sufficiently communicated on the project page.

Production build 0.71.5 2024