Skip to content

fix(blog): de-duplicate Prisma Compute series seriesIndex#7994

Merged
ankur-arch merged 1 commit into
mainfrom
fix/compute-blog-series-duplicate-index
Jul 1, 2026
Merged

fix(blog): de-duplicate Prisma Compute series seriesIndex#7994
ankur-arch merged 1 commit into
mainfrom
fix/compute-blog-series-duplicate-index

Conversation

@prisma-gremlin

@prisma-gremlin prisma-gremlin Bot commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

What & why

The Prisma Compute blog series (series: prisma-compute) had a duplicate seriesIndex: two posts — prisma-compute-time-synchronization and evaluating-object-storage-providers-for-prisma-compute — were both numbered 9. The series ordering logic in apps/blog/src/lib/series.ts sorts members by seriesIndex ascending, 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, from seriesIndex: 9 to seriesIndex: 10. Both posts share date: 2026-06-26, so the tie was broken by merge order: prisma-compute-time-synchronization (PR #7984) was merged first and keeps 9; evaluating-object-storage-providers-for-prisma-compute (PR #7985) was merged later and incorrectly reused 9, 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 110 across all ten posts:

seriesIndex slug
1 launching-prisma-compute-public-beta
2 bun-rust-rewrite-prisma-compute
3 prisma-compute-custom-domains
4 create-prisma-deploy-prisma-compute
5 prisma-compute-config-file
6 image-transformations-with-bun-on-prisma-compute
7 building-open-chat
8 price-the-work-not-the-workflow
9 prisma-compute-time-synchronization
10 evaluating-object-storage-providers-for-prisma-compute

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

  • Documentation
    • Updated the order of the blog post “Evaluating Object Storage Providers for Prisma Compute” in its series listing.

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.
@vercel

vercel Bot commented Jul 1, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
blog Ready Ready Preview, Comment Jul 1, 2026 12:36pm
docs Ready Ready Preview, Comment Jul 1, 2026 12:36pm
eclipse Ready Ready Preview, Comment Jul 1, 2026 12:36pm
site Ready Ready Preview, Comment Jul 1, 2026 12:36pm

Request Review

@coderabbitai

coderabbitai Bot commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 123f91b4-a6e7-4a67-b801-fffb88a5c46b

📥 Commits

Reviewing files that changed from the base of the PR and between 576e923 and ae8cfc9.

📒 Files selected for processing (1)
  • apps/blog/content/blog/evaluating-object-storage-providers-for-prisma-compute/index.mdx

Walkthrough

This change updates the seriesIndex frontmatter value from 9 to 10 in a single blog post MDX file about evaluating object storage providers for Prisma Compute.

Changes

Frontmatter Metadata Update

Layer / File(s) Summary
Update series index
apps/blog/content/blog/evaluating-object-storage-providers-for-prisma-compute/index.mdx
The seriesIndex frontmatter value is changed from 9 to 10.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

  • prisma/web#7943: Also updates seriesIndex frontmatter values for other Prisma Compute series blog posts.
  • prisma/web#7985: Adds the same blog post's MDX file that this PR modifies the frontmatter of.

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)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: fixing a duplicate Prisma Compute seriesIndex in the blog series.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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.

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

@argos-ci

argos-ci Bot commented Jul 1, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Argos notifications ↗︎

Build Status Details Updated (UTC)
default (Inspect) ✅ No changes detected 1 ignored Jul 1, 2026, 12:43 PM

@ankur-arch ankur-arch merged commit a6f69aa into main Jul 1, 2026
16 of 17 checks passed
@ankur-arch ankur-arch deleted the fix/compute-blog-series-duplicate-index branch July 1, 2026 12:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants