Problem/Motivation

A growing number of sites are being provided the 2.2.x branch as an upgrade option, despite it being defunct, and they are upgrading to it. This is because composer has no concept of an unsupported branch, but just provides the user with the highest matching version.

The 2.2.0 release was a mistake because it was being provided as an option to upgrade on Drupal 10 sites, despite the minimum supported core version being 11. As a result, the 3.0.x branch was created and released.

The missing step was to supersede the 2.2.x branch with the 2.3.x branch and provide all users of the 2.x branch a highest matching version to keep composer happy.

Steps to reproduce

See #3604931: Add explicit Composer dependencies to genpass

Proposed resolution

  • Revert all commits to 2.2.x branch so that it is equivalent to 2.1.x branch, supporting previous Drupal Core versions
  • Create new release as 2.3.x branch, superseding the 2.1.x and 2.2.x branches
  • Mark 2.1.x as unsupported in 2-4 weeks.

Remaining tasks

  • ✅ File an issue
  • ✅ Addition/Change/Update/Fix
  • ✅ Testing to ensure no regression
  • ✅ Credit contributors
  • ✅ Release notes snippet
  • ✅ Release
  • Mark 2.1.x as unsupported

User interface changes

  • N/A

API changes

  • N/A

Data model changes

  • N/A

Release notes snippet

  • N/A

Issue fork genpass-3605388

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

elc created an issue. See original summary.

elc opened merge request !56

  • elc committed cca66045 on 2.2.x 
    fix: #3605388 Revert 2.2.x branch back to 2.1.x

This reverts commits...
elc’s picture

elc commented
Issue summary: View changes
Status: Active » Postponed

Genpass 2.3.0 is released, superseding 2.1.x and 2.2.x.

Postponing for a couple of weeks to allow some time for updates before marking 2.1.x as unsupported.

elc’s picture

elc commented

The majority of 2.2.x branch users have moved onto the 2.3.0 release.

Not much movement on the 2.1.x users so will leave the branch supported for another 2 weeks.

elc’s picture

elc commented
Assigned: elc » Unassigned
Status: Postponed » Fixed

The 2.1.x branch is now marked as unsupported.

Move to 2.3.x releases if using Drupal 10, or to 3.0.x release for Drupal 11 & 12.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.