Improvements for Release Blog Posts

Open
#8,541 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Domain
build-system, ci-cd, release

Research direction

Start by locating the release post generator automation and the build matrix it uses. Verify how simultaneous releases become pull requests, how Static Builds are scheduled, and how security release posts are formatted; done means the three listed behaviors work correctly.

Written by the indexing model from the issue text.

Description

During today's security release, we identified a few issues with the current release post generator automation:

  1. When multiple releases are created at the same time, they are not merged into a single PR
  2. Static Builds are slow, and they aren't always needed for every build. We should split this into a seperate, non-required matrix.
  3. Security Release Posts are not properly formatted.
Dominant language
TypeScript
Stars
6.9k
Forks
6.5k
Avg merge
2d 9h
Merged PRs (30d)
29

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nodejs/nodejs.org

All issues in nodejs/nodejs.org

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.