You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I spend a lot of time figuring out the current month/date and where it is on this graph and only have an aproximate estimate, you could highlight the current date
While it wouldn't make sense to put a line in the SVG, on the webpage specifically, we could have some JS and CSS that overlays a red div on top of the SVG?
Reacted by Boris Verkhovskiy, Augustin Mauroy and Ulises Gascón
Reacted by Caner Akdas, Aviv Keller and Claudio Wunder
Adding a separate overlay does not make sense here. Introducing additional JS and CSS to draw a red line over the SVG adds extra complexity to the website that isn’t really necessary. The SVG itself should ideally communicate this information clearly, since it’s the source of truth for the visualization. By layering extra logic on top, we’d be creating a workaround that could break if the SVG changes, and it also makes the code harder to maintain. A cleaner solution would be to adjust the SVG directly so the information is visible without relying on external patches.
As I understand it, this graph is regenerated occasionally by someone at release wg. But we need this new graph to be regenerated automatically on a daily basis, I don’t know how we will do that.
As I understand it, this graph is regenerated occasionally by someone at release wg. But we need this new graph to be regenerated automatically on a daily basis, I don’t know how we will do that.
nit: it should be weekly rather than daily, that's an easy way to make it 7 times more energy efficient, and I doubt any humans would be able to spot the difference
Reacted by Augustin Mauroy, Jordan Harband, Aviv Keller and Claudio Wunder
nit: it should be weekly rather than daily, that's an easy way to make it 7 times more energy efficient, and I doubt any humans would be able to spot the difference
Activity
avivkeller commentedon Aug 22, 2025
The SVG comes from https://github.com/nodejs/Release/blob/main/schedule.svg
ljharb commentedon Aug 22, 2025
While it wouldn't make sense to put a line in the SVG, on the webpage specifically, we could have some JS and CSS that overlays a red div on top of the SVG?
avivkeller commentedon Aug 24, 2025
Adding a separate overlay does not make sense here. Introducing additional JS and CSS to draw a red line over the SVG adds extra complexity to the website that isn’t really necessary. The SVG itself should ideally communicate this information clearly, since it’s the source of truth for the visualization. By layering extra logic on top, we’d be creating a workaround that could break if the SVG changes, and it also makes the code harder to maintain. A cleaner solution would be to adjust the SVG directly so the information is visible without relying on external patches.
ovflowd commentedon Aug 25, 2025
Agreed. The SVG is generated on-demand, and this could just be part of the SVG itself. IMO, we could just generate two variants.
araujogui commentedon Aug 27, 2025
WIP nodejs/lts-schedule#27
araujogui commentedon Aug 27, 2025
As I understand it, this graph is regenerated occasionally by someone at release wg. But we need this new graph to be regenerated automatically on a daily basis, I don’t know how we will do that.
ovflowd commentedon Aug 28, 2025
GitHub Actions?
AugustinMauroy commentedon Aug 28, 2025
what about a next.js endpoint with a daily retaliated ?
aduh95 commentedon Aug 28, 2025
nit: it should be weekly rather than daily, that's an easy way to make it 7 times more energy efficient, and I doubt any humans would be able to spot the difference
ovflowd commentedon Aug 28, 2025
+1
araujogui commentedon Aug 29, 2025
I created the GitHub Action to generate svg and commit it weekly.
nodejs/Release#1119
ovflowd commentedon Aug 31, 2025
Thanks, Gui!
feat: add current date marker flag (#27)
avivkeller commentedon Oct 11, 2025
I'm closing this., since it's no longer actionable for the website team. Refer to the nodejs/Release repository for further actions