The message is seen on the Updates page at admin/reports/updates

I've just tested the beta release, but I suspect that this might be an issue for all releases due to pulling the initial 2.x release.

See https://skitch.com/funnymonkey/rfbhp/available-updates-content for a screenshot.

Comments

jgraham’s picture

jgraham commented

I can't set 2.1 as the recommended release.

Ideally users are either on 2.1 or 2.3-beta1. I have added the markup into the project page to link to the release as I do not have the option to set 2.1 or 2.3-beta1 as the recommended or supported releases.

bonobo’s picture

bonobo commented

I don't know if something has changed in the last few hours, but the 6.x-2.3-beta1 release is now showing up as up to date.

This happened after I updated two other modules (FileField and ImageField).

On a separate site, the 6.x-2.1 branch is still showing the "Not supported" message, and I'm wondering if that's stale data.

In any case, I suspect that this will get cleaned addressed with the next point release.

jgraham’s picture

jgraham commented

Yeah, and again I can't control the support status of 2.1. The next point release should resolve this.

bonobo’s picture

bonobo commented
Component: User interface » Miscellaneous
Status: Active » Postponed