blog: add Prisma Compute series tag to Vercel pricing post#8014
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughA single-line frontmatter addition adds ChangesFrontmatter Update
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
Well, this is about as low-risk as changes come — one line, one field, zero logic. It's the code review equivalent of checking someone spelled their own name correctly. Ship it. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Comment |
|
The latest updates on your projects. Learn more about Argos notifications ↗︎
|
Martin's post "Prisma Compute vs Vercel Pricing" (slug
prisma-compute-vs-vercel-pricing) was missing the frontmatter field that includes it in the Prisma Compute blog series (https://blog.prisma.io/blog/series/prisma-compute).Change
Added
series: prisma-computeto the post's YAML frontmatter.metaImagePath: "/prisma-compute-vs-vercel-pricing/imgs/meta.png" +series: prisma-compute tags: - "prisma-postgres" - "platform"How the format was determined
Inspected the 10 existing posts already in the Prisma Compute series (e.g.
launching-prisma-compute-public-beta,prisma-compute-time-synchronization,price-the-work-not-the-workflow,bun-rust-rewrite-prisma-compute,prisma-compute-custom-domains). Every one declares membership with the same field:series: prisma-compute(unquoted, matching the registry key). This was confirmed against the single source of truthapps/blog/src/lib/series-registry.ts, whose header states: "In each post in the series, setseries: <key>andseriesIndex: Nin the frontmatter." Membership is determined solely byseries === seriesKey(apps/blog/src/lib/series.ts);seriesIndexonly affects ordering and is optional, so only theseriesfield was added. The post (dated 2026-07-01) sorts last (11/11) by date, which is the correct position.Only the one frontmatter line was changed; the post body and all other frontmatter fields are untouched, and the YAML remains valid.
Created by Mohawk
Summary by CodeRabbit