Repository navigation
fix(prisma-postgres-upgrade): read versions from the Console, update the date notes for rc.23 - #39
Open
kristof-siket wants to merge 1 commit into
Open
kristof-siket wants to merge 1 commit into
kristof-siket wants to merge 1 commit into
Conversation
…the date notes for rc.23 The skill pinned prisma 8.0.0-rc.27 and @prisma/orm-postgres 8.0.0-rc.20 as "today's" Console versions. The Console now installs rc.33 and rc.23, and its date notes described rc.20 behavior that no longer holds. - Versions: use the exact versions the Console's message or setup pull request names; rc.33 / rc.23 is only an example. For apps not headed to Compute, match the pair through prisma's @prisma/orm-toolchain. - client-api-mapping: from rc.22, DateTime, @db.Timestamp and @db.Timestamptz read and write a Date again; @db.Date and @db.Time read as strings. From rc.21, @default(now()) and @updatedat are written by the client in UTC, so the database's time zone no longer matters. - Drop the time zone decision from "What the user does" and the checklist; README topic line to match. - Verified against: what was checked at rc.33 / rc.23. - version 2.0.1 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
kristof-siket
force-pushed
the
fix/postgres-upgrade-temporal-polyfill
branch
from
November 10, 2026 16:06
236125c to
1d4a1c0
Compare
kristof-siket
marked this pull request as ready for review
November 10, 2026 18:00
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.
Why
prisma-postgres-upgradepinnedprisma8.0.0-rc.27 and@prisma/orm-postgres8.0.0-rc.20 as the versions "today's" Console setup installs. The Console now installsprisma8.0.0-rc.33 and@prisma/orm-postgres8.0.0-rc.23 (PRISMA_CLI_VERSION/ORM_POSTGRES_VERSIONin pdp-control-planepackages/interactors/src/compute/planComposerSetup.ts). The skill's date notes also described rc.20 behavior that rc.21 and rc.22 changed.Prisma's code tasks service (pdp-control-plane) runs this skill to upgrade customer apps. In an eval on rc.20, the type check failed with
Cannot find namespace 'Temporal'in@prisma/orm-target-postgres. That error is specific to rc.20. From rc.21, those types importTemporalfromtemporal-specthemselves. So the fix is to install the Console's versions, not to add a polyfill step. An earlier version of this PR added atemporal-polyfillstep; it is removed.What changes
npm view prisma@<version> dependenciesnames the@prisma/orm-toolchainversion, and@prisma/orm-postgrestakes the same one (rc.27 → rc.20, rc.33 → rc.23). The@latestwarning now sayslatestcan move past the Console's Composer version. Todaylatestis rc.33 / rc.23.client-api-mapping.md, the old differences 3 and 4:DateTimeread as a string. From rc.22 it reads and writes a JavaScriptDatein UTC, as in 6/7. The new difference is that@db.Dateand@db.Timeread as strings.@default(now())in its own time zone. From rc.21 the client writes it in UTC, as 6/7 did, so it is no longer a difference. It is now a short note, which leaves four differences.prisma-8skill for older versions.metadata.version2.0.1.What I checked at rc.33 / rc.23
On Node.js 24.21 and PostgreSQL 18.6, I used a CommonJS app with a Prisma 6
schema.prismaand the table Prisma 6 migrate creates for it. The schema hasDateTime @default(now()),DateTime @updatedAt,@db.Timestamptz(3)and@db.Datefields. I set the database's time zone toAmerica/New_York.prisma contract emitandprisma db signwork. The contract usespg/timestamp-date@1forDateTime,pg/timestamptz-date@1for@db.Timestamptzandpg/date-string@1for@db.Date.tsc(TypeScript 5.9.3) passes on the skill'ssrc/db.tswith noTemporalpolyfill or types. The type check rejects assigning aDateTimefield to astring. The.d.mtsfiles in@prisma/orm-target-postgresimportTemporalfromtemporal-spec.Temporal:createdAt,updatedAtandpublishedAtread back asDate.dayreads as the string"2026-11-10".createdAtorupdatedAtstored16:04:53.601, the UTC time. The database's local time was11:04. An update movedupdatedAtforward.prisma db verify, the full agent run, and the query-mapping table were not re-checked at rc.23..first({ id })and.where(...).update(...)were used and work.🤖 Generated with Claude Code