Compute releaseDate and supportEndDate as the last Tuesday of the
relevant month (a fully-specified YYYY-MM-DD) instead of an approximate
YYYY-MM month, and convert the remaining vague values in versions.json
to their precise last-Tuesday equivalents.
---------
Co-authored-by: Loïc Guitaut <loic@discourse.org>
Merging this will trigger the creation of a `release/2026.4` branch on
the preceding commit.
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Merging this will trigger the creation of a `release/2026.3` branch on
the preceding commit.
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Merging this will trigger the creation of a `release/2026.2` branch on
the preceding commit.
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Merging this will trigger the creation of a `release/2026.1` branch on
the preceding commit.
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Also introduces a `versions.json` file which will be the source-of-truth
for versioning information for core automation, and for external systems
like `releases.discourse.org`.