feat: release schedule #195

clavin · 2025-11-02T01:45:13Z

Description of Change

Adds a schedule that shows key dates about major Electron releases:

Stable, beta, and alpha release dates
End-of-life dates
Chromium & Node.js versions

This information matches the manual table in the docs.

Checklist

This PR was not created with AI. (PRs created mainly with AI will be closed. They waste our team's time. We ban repeat offenders.)

clavin · 2025-11-02T02:05:15Z

Gonna see if I can split out the fullDate changes into their own PR, since they aren't necessary for this feature.

Edit: done!

clavin · 2025-11-02T02:19:26Z

app/routes/history.tsx


      <div className="bg-white dark:bg-gray-800 rounded-xl shadow-sm border border-gray-200 dark:border-gray-700 overflow-hidden mb-6">
-        <div className="p-4 border-b border-gray-200 dark:border-gray-700 bg-gray-50 dark:bg-gray-900/50 flex flex-wrap items-center gap-6">
+        <div className="p-4 border-gray-200 dark:border-gray-700 bg-gray-50 dark:bg-gray-900/50 flex flex-wrap items-center gap-6">


Drive-by touchup: this bottom border was redundant. (Looking again, I think the colors might be too? But at least it doesn't show now.)

app/data/release-schedule.ts

app/routes/schedule.tsx

MarshallOfSound · 2025-11-04T19:23:32Z

The release line that hasn't started yet should probably be opacity: 0.5 or something, not the same visual treatment as the active alpha line? Or maybe purple because it's nightly?

clavin · 2025-11-05T07:33:58Z

@MarshallOfSound fair! I added a separate purple theme for the nightly row in 99b5972. now they match the colors on the home page!

clavin · 2025-11-05T07:36:12Z

P.S. I added stripes to the nightly & prerelease rows because (1) I think they're cool and (2) they help disambiguate the green and yellow for deuteranopic color blindness (and verified this with my wonderful deuteranopic partner).

dsanders11

Absolutely love this.

I've wanted this data in programmatic form for years now (see #18 for an earlier attempt at just JSON output, which I later refactored on the versions-json-refactor branch). Non-blocking for this PR, but I'd want to also expose this data in the future via a /schedule.json endpoint - that's the last piece of the puzzle for putting proper dates into our Releases WG project board stable prep items. If we expose it as JSON I should be able to update the automation around templating to grab the right dates and fill them in for us.

I've left some inline comments, but a big meta one: tests? Some inspiration from the tests I was fleshing out on my branch. Namely we should test the edge cases (when alphas started, etc) and a snapshot in time of correct data would be nice so that we can change this code without risking missing subtle changes to the dates.

app/data/release-schedule.ts

app/root.tsx

dsanders11 · 2025-11-05T07:27:46Z

app/data/release-schedule.ts

+
+    return schedule;
+  },
+  getKeyvCache('absolute-schedule'),


I wish we had a way to cache this data more permanently, rather than being destined to recalculate the dates for old releases for the rest of time.

Maybe we could put the historical data into a JSON file in this repo, and this code could stop when it hits a major that's already in the committed historical data? Then it would still be dynamic, but occasionally one of us could update the historical data in the JSON file and save some CPU cycles on recalculating dates that shouldn't change.

Once we expose the data in JSON via /schedule.json, we could even have a scheduled workflow that automatically opens a PR to update the historical data JSON file once a release has passed EOL and the data will no longer change. Nice little feedback loop could happen there. 🙂

I'm a big fan of the model you're proposing over the one I implemented in this PR. We should definitely implement that system, as the schedule.json file would be very useful for other applications/systems.

app/data/release-schedule.ts

dsanders11 · 2025-11-05T07:41:15Z

app/data/release-schedule.ts

+      const latestRelease = group.releases[0];
+
+      const entry: AbsoluteMajorReleaseSchedule = {
+        version: `${major}.0.0`,


For discussion: do we really want the .0.0 suffix here, or just the major? Since the Node.js version shown is for the latest release in a major line, it's a bit misleading to show that Node.js version and the .0.0 version number, since that might cause confusion.

I'd be in favor of dropping the suffix and just going with the major numbers, personally. I don't think the static suffix on all of them adds any value (I know this is how we have it in the Markdown at the moment).

The Node.js version shown is for the *.0.0 release—unless there are no stable releases yet, in which case it uses the latest pre-release for that line.

You make a good point! Here's how I see it

In favor of keeping the suffix: it gives each row’s major “key” a strong visual anchor and helps clarify the nature of the data.

Against it: it adds noise and slightly constrains what we put in the table.

Not picky about which direction we take--just wanted to offer that perspective before changing it. With that context are you still leaning toward dropping the suffix?

The Node.js version shown is for the *.0.0 release—unless there are no stable releases yet, in which case it uses the latest pre-release for that line.

Ah, I misread the code, you're right. With that in mind, I'm fine leaving it with the .0.0 suffix for now.

Alternatively, we could make the suffix .x.y which would leave the visual anchor, but avoid any confusion about what info applies to the whole major line versus just the .0.0 version.

mlaurencin · 2025-11-05T18:03:59Z

app/routes/schedule.tsx

+      <div className="flex items-start gap-2 text-sm text-gray-500 dark:text-gray-500">
+        <Info className="w-4 h-4 mt-0.5 flex-shrink-0" />
+        <p>
+          Release dates are goals and may be adjusted at any time for significant reasons, such as


nit: Do we want to have this call out higher on the page instead? Realistically, I don't think someone is going to scroll all the way down and see this organically.

An alternative could be a sort of on hover info tooltip at the top. With "Release dates are goals and may be adjusted at anytime" with the longer description shown on hover.

Now correctly predicts alpha/beta dates for most versions. Deliberately corrects some beta release dates that were incorrectly published as Wednesday instead of Tuesday.

clavin · 2025-11-25T07:04:41Z

@dsanders11 Sorry -- need a fresh review after the merge commit 😄

clavin requested review from a team as code owners November 2, 2025 01:45

Remove redundant border on history page

c7f0ae6

clavin force-pushed the clavin/release-schedule branch from 83b8460 to 0f785fa Compare November 2, 2025 02:09

clavin added 3 commits November 1, 2025 19:10

Add schedule page, data fetching, caching, and estimation logic

0ebb7e6

Remove unclear + indicator, adjust disclaimer wording instead

f46447c

Simplify release-schedule.ts

ca86397

clavin force-pushed the clavin/release-schedule branch from 0f785fa to ca86397 Compare November 2, 2025 02:11

MarshallOfSound temporarily deployed to release-stat-clavin-rel-fxtid9 November 2, 2025 02:12 Inactive

clavin commented Nov 2, 2025

View reviewed changes

codebytere reviewed Nov 2, 2025

View reviewed changes

app/data/release-schedule.ts Outdated Show resolved Hide resolved

Use full semver for Node.js version

1b1ddeb

MarshallOfSound temporarily deployed to release-stat-clavin-rel-fxtid9 November 2, 2025 20:43 Inactive

codebytere approved these changes Nov 4, 2025

View reviewed changes

erickzhao reviewed Nov 4, 2025

View reviewed changes

app/routes/schedule.tsx Outdated Show resolved Hide resolved

app/routes/schedule.tsx Outdated Show resolved Hide resolved

app/routes/schedule.tsx Show resolved Hide resolved

clavin added 2 commits November 4, 2025 21:53

Link to Chrome & Node.js release notes

9ad78c8

Add unique background patterns for rows by status

5e50eb5

MarshallOfSound temporarily deployed to release-stat-clavin-rel-vrenti November 5, 2025 06:42 Inactive

Unify text size in rows

674907a

MarshallOfSound temporarily deployed to release-stat-clavin-rel-vrenti November 5, 2025 06:44 Inactive

Simplify styles

c7350ee

MarshallOfSound temporarily deployed to release-stat-clavin-rel-vrenti November 5, 2025 07:10 Inactive

Add nightly and rename 'active to 'stable'

99b5972

MarshallOfSound temporarily deployed to release-stat-clavin-rel-vrenti November 5, 2025 07:26 Inactive

dsanders11 requested changes Nov 5, 2025

View reviewed changes

Add EOL override for E22

5d0b3cc

mlaurencin reviewed Nov 5, 2025

View reviewed changes

dsanders11 approved these changes Nov 23, 2025

View reviewed changes

Simplify, improve accuracy, add overrides

d428327

Now correctly predicts alpha/beta dates for most versions. Deliberately corrects some beta release dates that were incorrectly published as Wednesday instead of Tuesday.

MarshallOfSound temporarily deployed to release-stat-clavin-rel-cs7uch November 25, 2025 06:56 Inactive

Merge remote-tracking branch 'origin/main' into clavin/release-schedule

d61fa84

MarshallOfSound temporarily deployed to release-stat-clavin-rel-cs7uch November 25, 2025 06:58 Inactive

clavin requested a review from dsanders11 November 25, 2025 07:03

dsanders11 approved these changes Nov 25, 2025

View reviewed changes

ckerr approved these changes Nov 25, 2025

View reviewed changes

erickzhao approved these changes Nov 25, 2025

View reviewed changes

codebytere merged commit 1b3fb43 into main Nov 26, 2025
4 checks passed

codebytere deleted the clavin/release-schedule branch November 26, 2025 05:27

feat: release schedule #195

feat: release schedule #195

Uh oh!

Conversation

clavin commented Nov 2, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description of Change

Checklist

Uh oh!

clavin commented Nov 2, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

MarshallOfSound commented Nov 4, 2025

Uh oh!

clavin commented Nov 5, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

clavin commented Nov 5, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

dsanders11 left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

clavin commented Nov 25, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

8 participants

clavin commented Nov 2, 2025 •

edited

Loading

clavin commented Nov 2, 2025 •

edited

Loading

clavin commented Nov 5, 2025 •

edited

Loading

clavin commented Nov 5, 2025 •

edited

Loading

dsanders11 left a comment •

edited

Loading

clavin commented Nov 25, 2025 •

edited

Loading