content(releases): add /releases section with May 2026 release page#19189
Conversation
Introduces a new top-level /releases/ section as a running log of major Pulumi platform updates, with the May 2026 "Building for the agentic infrastructure era" release as the first entry. Adds list + single layouts and a set of reusable partials so future releases can be authored entirely from frontmatter. Wires Releases into the main header nav (under "For engineers") and the footer, and tweaks baseof.html so the footer pins to the bottom on short pages. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Pre-merge Review — Last updated 2026-05-19T21:19:23ZTip Summary: This PR introduces a brand-new Review confidence:
Investigation log
🔍 Verification trail57 claims extracted · 14 verified · 7 unverifiable · 2 contradicted
----- PINNED-COMMENT-DELIMITER ----- 💡 Pre-existing issues in touched files (optional)No pre-existing issues in touched files. ✅ Resolved since last review
📜 Review history
Need a re-review? Want to dispute a finding? Mention 🚨 Outstanding in this PRNo outstanding issues remain.
|
|
Your site preview for commit 5a27212 is ready! 🎉 http://www-testing-pulumi-docs-origin-pr-19189-5a27212f.s3-website.us-west-2.amazonaws.com |
Lighthouse Performance ReportCommit: 5a27212 | Metric definitions
|
|
Re: Quote - https://www.pulumi.com/blog/the-agentic-infrastructure-era/ Exact quote is: "At the same time, we’re seeing something magical happen here at Pulumi: LLMs are now doing 20% of the infrastructure deployments, up from virtually zero a year ago. We expect this to grow to over 50% before the end of this year and well beyond afterwards. " Re: Blog post - published and exists at https://www.pulumi.com/blog/10-more-things-you-can-do-with-neo/ |
|
Claude finished @jeffmerrick's task in 1m 11s —— View job Thanks for the clarifications, @jeffmerrick — both 🚨 Outstanding items from the automated review are now resolved. Duffy quote (L19-21)The primary source (your blog post) does contain the "over 50% before the end of this year" language exactly:
The automated review flagged a mismatch because it was comparing against The New Stack's secondary paraphrase ("100 percent in the future") rather than the canonical Pulumi blog post. Since the One minor note: the displayed quote in the content file (L19-21) omits the trailing "and well beyond afterwards." That phrase is meaningful context (it signals 50% is a milestone, not a ceiling), so you might consider keeping the full sentence: intro:
quote: |
"LLMs are now doing 20% of the infrastructure deployments, up from
virtually zero a year ago. We expect this to grow to over 50% before
the end of this year and well beyond afterwards."Not a blocker — truncation for display is normal — just something to consider. Blog post URL (L152)
Both 🚨 Outstanding items are cleared. The |
Corrects invalid negative-margin classes on the intro/TOC row, removes the redundant `description` field in the releases _index, fixes a variable name typo, and drops a duplicate responsive heading class. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
|
@claude #update-review |
|
🤖 Review updated on @CamSoper's request. |
|
@claude resolve the outstanding findings per #19189 (comment) and #19189 (comment) and then #update-review |
|
Hey @jeffmerrick! Thanks for playing along with my review bot! Sorry I've been making noise on your PR, but I wanted to test something. So I fired off a simple Anyway, my second attempt is the way to do it. I'll work on figuring out a fallback for when people forget. Thank you again for being a good sport (and guinea pig) and I'm sorry for the noise! |
|
🤖 Review updated on @CamSoper's request. |
|
@CamSoper Ah, I misread the instructions. No worries at all! |
51e876f to
9227bbb
Compare
9227bbb to
5a27212
Compare

Adds releases, a isting page and detail page for major feature announcements.
I have linked it in the main nav under 'For engineers' and the footer under 'Resources'. It probably doesn't have to live in the main nav if we'd prefer to use promo spots (hero, announcement bar) to promote it when there is a new release.
I've linked the cards on the release page I could find links for, others may still need some (in addition to the ones we'll need to add as more blog posts are published.)
Generated description of changes:
Summary
/releases/section as a running log of major Pulumi platform updates, with the first entry: the May 2026 "Building for the agentic infrastructure era" release.releaseslist + single layouts and a set of reusable partials (hero-card,intro-toc-row,section,card,card-text-block,release-item,blog-list) so future releases can be authored entirely from frontmatter.Releasesinto the main header nav (under "For engineers") and the site footer.baseof.htmlto make<body>amin-h-screen flex flex-colso the footer pins to the bottom on short pages like the new releases index.Screens
/releases/— index of all releases (onerelease-itemper page, newest first)./releases/agentic-infrastructure-era/— dark hero card, intro + sticky TOC row, four sections with mixed text/image cards, and a "More from the blog" list at the bottom.Test plan
make serveand visit/releases/— verify the May 2026 release renders as a single card and links into the detail page./releases/agentic-infrastructure-era/— verify hero, TOC anchors scroll to the right sections, all card variants (text,image-top,image-left,image-right) render correctly, and the "More from the blog" rows link to the referenced posts.Releasesentry appears in the header nav under "For engineers" and in the footer.baseof.htmlflex change hasn't shifted existing layouts./releases/agentic-infrastructure-era/oncestatic/images/releases/may-2026/meta.pnglands.make lintpasses.Resolves https://github.com/pulumi/marketing/issues/1748.