Skip to content

fix: align release post frontmatter with blog layout - #276

Merged
avivkeller merged 1 commit into
webpack:mainfrom
sameerchore:fix/release-post-frontmatter
Sep 23, 2026
Merged

avivkeller merged 1 commit into
webpack:mainfrom
sameerchore:fix/release-post-frontmatter

Conversation

@sameerchore

@sameerchore sameerchore commented Sep 22, 2026 •

Copy link
Copy Markdown
Contributor

Summary

This PR fixes the frontmatter generated for automated webpack release blog posts.

The template used layout: blog-post and author, but the website expects layout: post and authors. This could cause release posts to use the wrong layout or fail to display author information.

What kind of change does this PR introduce?

This is a bug fix.

Did you add tests for your changes?

No new automated tests were added because this is a two-line template correction.

Validation performed:

  • Existing test suite passed.
  • Prettier check passed.
  • Generated frontmatter was manually verified.

Does this PR introduce a breaking change?

No. This only makes newly generated release posts match the existing blog format.

If relevant, what needs to be documented once your changes are merged or what have you already documented?

No documentation changes are required.

Use of AI

Yes by Ai I identify frontmatter mismatch, make the minimal change, and run validation checks. I reviewed the generated output and verified the final change while being in the loop manually .

Summary by CodeRabbit

  • Documentation
    • Updated the release blog post template metadata to use the standard post layout.
    • Renamed the author metadata field to support the updated format.

@vercel

vercel Bot commented Sep 22, 2026 •

Copy link
Copy Markdown

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

Project Deployment Actions Updated
webpack-doc-kit Ready Ready Preview Sep 22, 2026 4:04pm UTC

Request Review

@coderabbitai

coderabbitai Bot commented Sep 22, 2026

Copy link
Copy Markdown

Review in Change Stack →

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 6ead4ff4-c3c8-4449-ab61-4b53b402606d

📥 Commits

Reviewing files that changed from the base of the PR and between c51e093 and a10d4fe.

📒 Files selected for processing (1)
  • scripts/release/template.md.hbs

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.


Walkthrough

The release blog post template now uses the post layout and the authors front matter field. A blank line was added after the closing {{/with}} block.

Priority: ⬇️ Low

Merge Risk: ⚪ Minimal · up to a10d4

Generated release posts will use the existing post layout and preserve author information under the authors field. The change is ready to merge.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely describes the frontmatter alignment for generated release posts, which is the main change.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create a new PR

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@avivkeller
avivkeller merged commit b37a1c8 into webpack:main Sep 23, 2026
14 checks passed

This branch was successfully deployed

1 active deployment
Preview — a10d4fea Deployed Sep 22, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants