Only show RC pre-releases of core in the form

@tedbow and @tim.plunkett discussed the plan for getting Automatic Updates, Project Browser and Package Manager into core. We're likely going to aim to land Package Manager first. So postponing this issue for now, until the dust settles on that.

I don't think this needs to be postponed anymore since most of the package manager alpha blockers aren't currently actionable. However, what's the difference between this issue and 📌 Limit non-stable releases to RCs on updater form Closed: duplicate ? Is this one about pre-releases of core and the other one about pre-releases of contrib projects?

Closed 📌 Limit non-stable releases to RCs on updater form Closed: duplicate as duplicated.

Only I had commented on that issue:

We have \Drupal\automatic_updates\Validator\VersionPolicy\TargetVersionStable
but this only applies for cron

We actually test that pre-release shows up for the next minor in \Drupal\Tests\automatic_updates\Functional\UpdaterFormTest::testNextMinorPreRelease but we don't test alpha. I think an alpha would show for the next release

I think we at least need to allow updating to RC releases of the next minor because otherwise you would have a very narrow window in which you could update from you current minor to current minor +2. I would think we would want that so people could rely on cron updates from 1 year.

Pushed up a validator for only RC1 and above. Need to add a test that beta and below are not supported

@phenaproxima back to you

Very few notes here -- the original MR looks pretty good.

I'm not super hot on having two separate policy rules for this, but I think it's the simplest thing we could do (we tried making it more flexible but that created more problems than it solved).

phenaproxima → closed merge request !977

@phenaproxima added todo to 📌 Remove UpdateStage::begin() in favor of ::create() Active I think this is ready for review again

Okay, makes sense to me.

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