Core compatibility messages on contrib available updates should consider supported branches

Created on 12 February 2020, almost 5 years ago
Updated 1 May 2024, 8 months ago

Problem/Motivation

Discovered in #3111929: If no recommended update is found, Update Status recommends the latest release, even if it is unsupported where a release was added to the XML update fixtures.

The release 8.2.0 was before any of the expected updates but it was not in an unsupported branch.
This broke the asserts in \Drupal\Tests\update\Functional\UpdateContribTest::testCoreCompatibilityMessage() because it changed the message from

This module is compatible with Drupal core: 8.0.0 to 8.1.1

to

This module is compatible with Drupal core: 8.0.0 to 8.2.0

This should not have change the message because we shouldn't consider 8.2.0 for the message because it is unsupported.

This is very unlikely to actually happen in core because we don't have new releases in unsupported branches.

Proposed resolution

Don't use unsupported core releases when creating the core compatibility messages on the updates report

Remaining tasks

fix it

User interface changes

Before

After

API changes

Data model changes

Release notes snippet

🐛 Bug report
Status

Fixed

Version

10.3

Component
Update 

Last updated 6 days ago

  • Maintained by
  • 🇺🇸United States @tedbow
  • 🇺🇸United States @dww
Created by

🇺🇸United States tedbow Ithaca, NY, USA

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

Merge Requests

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024