refactor: updated release script and updated shiki

[ovflowd]

Description

This PR cleans up and refactors the Node.js Release Blog Post generation script.

• Modernizes the code a little bit
• Cleanses the code
• Updates the code by removing a few outdated things (regex replacements, version checks, and other things)
• Fixes occasional "Coming Soon" due to using "direct.nodejs.org"
• More obvious promisification of pieces of the code
• Already transforms the * lists into - lists (sadly prettier does not allow this to be changed)
• Adds ShellScript and ShellSession Shiki Languages

Validation

Generating the Blog Posts should still work (for latest version, specific version, and forced generation)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
nodejs-org	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 14, 2023 9:02am

[ovflowd]

cc @tniessen @nodejs/web-infra

[tniessen]

RSLGTM :)

[github-actions]

Unit Test Coverage Report

Lines	Statements	Branches	Functions
	94.68% (267/282)	78.12% (50/64)	92.98% (53/57)

Unit Test Report

Tests	Skipped	Failures	Errors	Time
27	0 💤	0 ❌	0 🔥	5.646s ⏱️

[bmuenzenmeyer]

read through it - also ran the current release post again

✅

[richardlau]

The preview link is showing a 500 error?

[richardlau]

* Fixes occasional "Coming Soon" due to using "direct.nodejs.org"

History is that we switched to using direct because of "Coming Soon"'s occurring: #4136
This will be very hard to validate/test outside of a release.

[bmuenzenmeyer]

The preview link is showing a 500 error?

I'm guessing that's a hiccup - local and CI deploy and serve scripts run fine and this changeset doesn't appear to have anything related to next deployment. 🤞

@ovflowd or someone else with Vercel access can look into it (I still do not)

[ovflowd]

* Fixes occasional "Coming Soon" due to using "direct.nodejs.org"

History is that we switched to using direct because of "Coming Soon"'s occurring: #4136 This will be very hard to validate/test outside of a release.

Right. But that's the source of flakiness. The thing is that direct.nodejs.org is less reliable, as it is a non-cached origin. Not to mention once we move to R2, direct.nodejs.org is not an endpoint we want to hit.

[ovflowd]

The preview link is showing a 500 error?

I'm guessing that's a hiccup - local and CI deploy and serve scripts run fine and this changeset doesn't appear to have anything related to next deployment. 🤞

@ovflowd or someone else with Vercel access can look into it (I still do not)

Yea, I fixed the issue. It was shiki's embeddedLangs. Apparently it completely ignores the language grammar I am providing and tries to use its "built-in" resolution.

Removing embeddedLangs surprisingly doesn't break the highlighting, and apparently it is only used to pre-load other languages before the one you're currently loading. But since our shiki.config.mjs is already ordered, all fine. I swear, I hate when popular libraries depend on filesystem or other internals and give little to none control to end-users (I had to dig deep in order to make this shiki.config.mjs to work to begin with.

[RafaelGSS]

LGTM

[richardlau]

* Fixes occasional "Coming Soon" due to using "direct.nodejs.org"

History is that we switched to using direct because of "Coming Soon"'s occurring: #4136 This will be very hard to validate/test outside of a release.

Right. But that's the source of flakiness. The thing is that direct.nodejs.org is less reliable, as it is a non-cached origin. Not to mention once we move to R2, direct.nodejs.org is not an endpoint we want to hit.

Yes, being non-cached was the point behind the original switch. Maybe it's not an issue now with the tweaks that were made to avoid caching 404's.

[ovflowd]

* Fixes occasional "Coming Soon" due to using "direct.nodejs.org"

History is that we switched to using direct because of "Coming Soon"'s occurring: #4136 This will be very hard to validate/test outside of a release.

Right. But that's the source of flakiness. The thing is that direct.nodejs.org is less reliable, as it is a non-cached origin. Not to mention once we move to R2, direct.nodejs.org is not an endpoint we want to hit.

Yes, being non-cached was the point behind the original switch. Maybe it's not an issue now with the tweaks that were made to avoid caching 404's.

Right. I'll keep an eye on that once a next release is done!

[targos]

I'm releasing v21.1.0 and hit two "coming soon" links and no shasums in the generated changelog.

[targos]

Rerunning a couple times fixed it, but it seems that the warning that used to be printed is no longer here so this is prone to errors if the generated file is not verified.

[ovflowd]

Rerunning a couple times fixed it, but it seems that the warning that used to be printed is no longer here so this is prone to errors if the generated file is not verified.

Heyo, 👋 which warnings?

The rerunning is due to Cloudflare giving errors probably a cache purge happened recently.

[targos]

which warnings?

The script used to print warnings to the console when there were lines with "coming soon".

[ovflowd]

which warnings?

The script used to print warnings to the console when there were lines with "coming soon".

It should still be doing that if the request failed. But I can double-check. Afaik if the request failed (i.e. it will trigger a coming soon) it should console.warn that it failed. Will give a double check over here.

[targos]

@richardlau also had two "coming soon" links. Did you see a warning?

[richardlau]

@richardlau also had two "coming soon" links. Did you see a warning?

No, no warnings.