feat(cicd): automate the creation of blog posts

[avivkeller]

cc @nodejs/releasers

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Updated (UTC)
nodejs-org	Ready	Preview	Oct 21, 2025 8:38pm

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 76.52%. Comparing base (bd92fd2) to head (ae9313c).
⚠️ Report is 14 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@ Coverage Diff @@## main #8231 +/- ##
==========================================
+ Coverage 76.39% 76.52% +0.12% 
==========================================
Files 115 117 +2 Lines 9643 9733 +90 Branches 318 330 +12 ==========================================
+ Hits 7367 7448 +81 - Misses 2275 2283 +8 - Partials 1 2 +1 

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[avivkeller]

blocked by nodejs/admin#1016

[Copilot]

Pull Request Overview

Automate creating release blog posts and opening a PR via GitHub Actions.

• Update the release-post script to return both the file path and metadata so the workflow can capture the version.
• Add a GitHub Actions workflow to run the script and open/update a PR with the new blog post.

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
apps/site/scripts/release-post/index.mjs	Adjusts writeToFile to resolve both path and results; logs and emits version for workflow consumption.
.github/workflows/create-release-post.yml	New workflow to generate a release post and open a PR, using a pinned action and step outputs.

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[avivkeller]

The passing of an input version is no longer optional, and a draft PR is used in place of requiring a custom token

[avivkeller]

@mcollina could you please take another look?

[mcollina]

lgtm

[marco-ippolito]

Just a random idea, maybe we could trigger automatically when a release is created on nodejs/node with https://docs.github.com/en/webhooks/webhook-events-and-payloads#repository_dispatch

[richardlau]

Just a random idea, maybe we could trigger automatically when a release is created on nodejs/node with https://docs.github.com/en/webhooks/webhook-events-and-payloads#repository_dispatch

I think that's worth exploring separately from this. Just having this (and being able to manually trigger) would be a good stepping point -- for me creating the blog posts is currently one of the more time consuming parts of the release process on release day (due to needing to switch to a dev environment with pnpm and Husky pre-commit hooks).

[MattIPv4]

Just a random idea, maybe we could trigger automatically when a release is created on nodejs/node with https://docs.github.com/en/webhooks/webhook-events-and-payloads#repository_dispatch

Can this be triggered from https://github.com/nodejs/node/blob/main/.github/workflows/update-release-links.yml, which is the same automation that triggers the release worker to update the files available when a new release is cut?

[avivkeller]

That's the plan I had in mind

[avivkeller]

See nodejs/node#60366

[avivkeller]

@nodejs/web-infra

The action gr2m/create-or-update-pull-request-action@b65137ca591da0b9f43bad7b24df13050ea45d1b is not allowed in nodejs/nodejs.org because all actions must be from a repository owned by your enterprise, created by GitHub, or match one of the patterns: LoveToKnow/slackify-markdown-action@*, MishaKav/jest-coverage-comment@*, actions-ecosystem/action-remove-labels@*, chromaui/action@*, codecov/codecov-action@*, codecov/test-results-action@*, crowdin/github-action@*, ossf/scorecard-action@*, patrickedqvist/wait-for-vercel-preview@*, pnpm/action-setup@*, rtCamp/action-slack-notify@*, stefanzweifel/git-auto-commit-action@*, step-security/harden-runner@*, thollander/actions-comment-pull-request@*, treosh/lighthouse-ci-action@*.

[MattIPv4]

We cannot fix that, new actions need to be added to the repo settings by @ovflowd or @bmuenzenmeyer (I don't see the web-admin team yet)

[bmuenzenmeyer]

We cannot fix that, new actions need to be added to the repo settings by @ovflowd or @bmuenzenmeyer (I don't see the web-admin team yet)

added