What happened?

1. Query the GitHub Releases API for this repository:
   https://api.github.com/repos/joomla/joomla-cms/releases
2. Find the entry for tag 6.2.0-beta2.
3. It returns "prerelease": false.

The release is titled "Joomla! 6.2.0 Beta 2", but the API reports it as a
normal (non-pre-release) release. Tooling that offers Joomla versions to
users typically filters this feed on the prerelease flag, so the beta is
presented as though it were a stable release.

Because 6.2.0-beta2 also sorts above 6.1.3 numerically, it can displace
the current stable 6.x release at the top of a version list rather than just
appearing alongside it.

Version

6.2

Expected result

6.2.0-beta2 reports "prerelease": true, consistent with every other
alpha, beta and RC tag in the repository.

Actual result

6.2.0-beta2 reports "prerelease": false.

System Information

Not applicable. This is release metadata on GitHub, not CMS behaviour.

Additional Comments

This looks like a one-off slip rather than a process problem. Of the 67
alpha/beta/RC tags in the most recent 100 releases (back to 5.2.2-rc1,
November 2024), 66 are correctly flagged. 6.2.0-beta2 is the only one
that is not.

One detail suggests the rest of the release was published correctly:
GET /releases/latest still returns 6.1.3, not 6.2.0-beta2, even
though 6.2.0-beta2 is a non-pre-release with a newer created_at. So the
"latest release" pointer was withheld from the beta as intended, and only
the pre-release flag appears to have been missed.

Fix should be a single change on the existing release (edit the release,
tick "Set as a pre-release"). No code change is involved and there is
nothing to patch in the repository, which is why this is an issue rather
than a pull request.

Happy to close this if the flag is intentional for beta2 and I have
misread the intent.