Add tests for updates should not recommend a new branch if there are no stable releases

Adding screenshot from my local 9.5.11 site showing the bug.

Too late to fix this for 9.5 sites, even if we backported something they'd need to update to the newer 9.5 release to get 10.x recommended.

However given we're planning to support 10.x right up until around 12.0.0's release, this is more likely to happen again since the Drupal 10 EOL will be a lot closer to 12.0.0's release date. A bit of time before we get there, but moving to major.

Also just run into this on a small site that was way behind and has just been updated to 9.5.11, it's also recommending going to 11.0.0-rc1 or 10.2.2 as a security update, and doesn't mention 10.3 at all.

On 11.x, I changed the Drupal version to 9.5.11 and checked for updates. Here are the results.

The new test uses a release history with only the supported releases, 10.2.0, 10.2.2, 11.0.0-alpha1, and 11.0.0-beta1. And runs with an installed release of 9.x.y, And a sample output from the test.

Those indicate this is fixed, although I don't know when.

This was solved in 🐛 Never show a "Not supported!" version as "Recommended" Needs work . I just patched my 9.5 site with the changes from that issue and get a better message:

So if this is fixed in newer versions and there is nothing now that can be done in 9.5, I think this can be closed as duplicate?

@longwave, thanks for identifying what issue fixed this problem.

I do think that the test case added here should be added. The test fixture added here is different from the existing ones in that it has a Major+2 version with alpha and beta releases. I am setting to Active to self review and add comments.

I changed the release numbers in the test fixtures to be more like what is already in the fixture directory. And added comments.

Additional test coverage is always good

Imagine if Microsoft thought about that :)

Committed/pushed to 11.x and cherry-picked back through to 10.3.x, thanks!

catch → closed merge request !8895

Automatically closed - issue fixed for 2 weeks with no activity.