All status pages · Unowned issues across all projects · How to write a weekly status report from GitHub

Weekly status: prisma/prisma

2026-10-08 to 2026-10-15 (7 days). Unofficial: generated from this repository’s public GitHub activity by pilotless status. Not affiliated with the project, and no information here that GitHub does not publish.

49 commits by 2 people, at least 38 pull requests merged, 100 open pull requests, 54 open issues on this page of results.

Stalled pull requests

Open, and untouched for seven days or more:

#29666 fix(conversion): add TIMESTAMPTZ support for date formatting - last touched 79 days ago
#29655 perf(client): expose Prisma Client performance branch - last touched 79 days ago
#29658 perf(client-engine): split render and data-mapper prerequisites - last touched 79 days ago
#29586 feat(migrate): add –no-hints flag to migrate deploy and migrate status - last touched 79 days ago
#29491 fix(adapter-mssql): surface socket errors as typed MappedError instead of throwing raw - last touched 79 days ago

Issues nobody has picked up

Open, unassigned, and with no replies yet:

#30722 Postgres unbound namespace with tables loses search_path resolution when contract.json is - opened 0 days ago
#30713 Prisma 7: Accelerate requests are no longer retried on transient failures (regression from - opened 1 days ago
#30688 orm init: say where to get a Postgres database and how to deploy - opened 3 days ago
#30645 Large schemas: new PrismaClient() eagerly deserializes the full ParamGraph, so construct - opened 7 days ago
#30640 Since 7.4.0, PostgreSQL migrations are no longer applied atomically (each statement commit - opened 7 days ago

The two lists above are what a status meeting is usually for. Nobody had to attend one to produce this page.

If you maintain prisma/prisma and would rather this page did not exist, open an issue and it will be deleted - no argument, no reply needed beyond the repository name.

Want this for your own repositories? Install the pilotless GitHub App — one click, then a pinned weekly status digest in each selected repo. Prefer CI-only? The status-action is still two lines of YAML with no account and nothing leaving GitHub.