Repository navigation
site(changelog): fix the area filter and make it multi-select - #8743
Closed
ankur-arch wants to merge 1 commit into
Closed
ankur-arch wants to merge 1 commit into
ankur-arch wants to merge 1 commit into
Conversation
…select filter Each entry was assigned one product area, so an entry tagged Compute and Postgres only showed under Compute, and the ORM filter listed 14 of the 47 ORM-tagged entries. Entries now carry every matching area and the filter pills toggle; an entry shows when it is in any selected area. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
ankur-arch
had a problem deploying
to
prisma-preview/site/changelog-filter-multiselect
November 4, 2026 13:54 — with 
GitHub Actions
Failure
GitHub Actions
Failure
Contributor
Author
|
Folded into #8741 as the same commit, so the fixed filter ships with the entries that exposed it. |
Contributor
|
Caution Review failedThe pull request is closed.
|
This branch had an error being deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The changelog filter hid most entries. Each entry was assigned one product area, picked by a priority list, so an entry tagged both Prisma Compute and Prisma Postgres only appeared under Compute, and one tagged Prisma ORM and Prisma Postgres only under Postgres. Selecting ORM showed 14 of the 47 entries tagged with it, and Postgres 27 of 33.
Now an entry belongs to every area its tags name, and the filter is multi-select.
What changed
categoriesForTagsinchangelog-meta.tsreturns every area an entry's tags name, most specific first.categoryForTagskeeps returning the first one, which still colours the card, so the timeline looks the same.changelog-meta.test.ts: multi-area entries, colouring order, platform fallback.Checks
Site test suite, type check, and oxfmt/oxlint on the changed files pass. The remaining findings in
changelog-hero.tsxandchangelog/[slug]/page.tsxare pre-existing and untouched. Not checked in a browser; the feed logic is covered by the unit tests.