ci: regenerate release svg automatically

[araujogui]

Related nodejs/nodejs.org#8101

Create a workflow to automatically re-generate the release schedule SVG weekly.

[nschonni]

I think it would make sense to create a PR when there is something changed. I wouldn't go redo this because of this suggestion, but you can see a similar workflow in the docker-node repo

[araujogui]

I think it would make sense to create a PR when there is something changed. I wouldn't go redo this because of this suggestion, but you can see a similar workflow in the docker-node repo

Well, that makes sense, but @nodejs/releasers would have to check, approve the pr and merge every Monday (obligatorily).

[AugustinMauroy]

LGMT !

[ovflowd]

PR looks good to me, but can we get someone from @nodejs/releasers to check this and agree that auto merge is OK?

[targos]

Direct push to main sounds scary, especially since this downloads 3rd-party packages from npm (through npx lts and npx svgo).

[targos]

Currently the main branch is not protected by rulesets but I think we should change that (breaking the workflow proposed here).

[araujogui]

Currently the main branch is not protected by rulesets but I think we should change that (breaking the workflow proposed here).

Got it, issue fixed. I also pinned package versions

[octavio12345300]

listo

[araujogui]

CC @nodejs/releasers

[aduh95]

I don't think this is worth it, it feels like it's going to be very noisy for little value IMO, and the hard coded version in the npx calls are going to be annoying to maintain. IMO the current process is better, despite being manual.
How big of a deal is it if this repo is updated manually every once in a while?

[araujogui]

I don't think this is worth it, it feels like it's going to be very noisy for little value IMO, and the hard coded version in the npx calls are going to be annoying to maintain. IMO the current process is better, despite being manual. How big of a deal is it if this repo is updated manually every once in a while?

I don't see any problem, but if anyone don't update the SVG in a while, the website will start displaying misleading info

[aduh95]

the website will start displaying misleading info

The website can (should) generate its own SVG, there's no reason to use the one in this repo

[araujogui]

the website will start displaying misleading info

The website can (should) generate its own SVG, there's no reason to use the one in this repo

what do you think @nodejs/nodejs-website? any concerns?