fix(blog): de-duplicate Prisma Compute series seriesIndex#7994
Conversation
Two Prisma Compute series posts shared seriesIndex: 9 (prisma-compute-time-synchronization and evaluating-object-storage-providers-for-prisma-compute). Renumber the later-merged post (PR #7985) from 9 to 10 so the series runs a unique, sequential, gap-free 1-10 across all ten posts.
|
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)
WalkthroughThis change updates the ChangesFrontmatter Metadata Update
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
Well, as a principal engineer, I can confirm this is about as low-risk as changes come — a single digit incremented in frontmatter metadata, correctly reordering the post within its series. No logic, no structure, just a number doing its job. Approved with a smile. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Comment |
|
The latest updates on your projects. Learn more about Argos notifications ↗︎
|
What & why
The Prisma Compute blog series (
series: prisma-compute) had a duplicateseriesIndex: two posts —prisma-compute-time-synchronizationandevaluating-object-storage-providers-for-prisma-compute— were both numbered9. The series ordering logic inapps/blog/src/lib/series.tssorts members byseriesIndexascending, so a collision produced an ambiguous/incorrect series order on the site.Fix
Renumbered the later-merged post,
evaluating-object-storage-providers-for-prisma-compute, fromseriesIndex: 9toseriesIndex: 10. Both posts sharedate: 2026-06-26, so the tie was broken by merge order:prisma-compute-time-synchronization(PR #7984) was merged first and keeps9;evaluating-object-storage-providers-for-prisma-compute(PR #7985) was merged later and incorrectly reused9, so it moves to the next free index. This is a single-value change with no reshuffling of the existing 1–9 order.The Prisma Compute series now runs a unique, sequential, gap-free
1–10across all ten posts:Scope
One frontmatter value in one MDX file. No changes to titles, slugs, dates, body content, or any other series.
Created by Mohawk
Summary by CodeRabbit