Improvements for Release Blog Posts
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.9k
- Forks
- 6.5k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 29
Description
During today's security release, we identified a few issues with the current release post generator automation:
- When multiple releases are created at the same time, they are not merged into a single PR
- Static Builds are slow, and they aren't always needed for every build. We should split this into a seperate, non-required matrix.
- Security Release Posts are not properly formatted.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
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.
Assessment
- Domain
- build-system, ci-cd, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100