chore: update npm provenance repository by StevenMcClankerton · Pull Request #30145 · prisma/orm · GitHub
Skip to content

chore: update npm provenance repository - #30145

Merged
SevInf merged 1 commit into
mainfrom
chore/update-npm-provenance-main
Aug 26, 2026
Merged

chore: update npm provenance repository#30145
SevInf merged 1 commit into
mainfrom
chore/update-npm-provenance-main

Conversation

@StevenMcClankerton

@StevenMcClankerton StevenMcClankerton commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

Summary

  • update package repository metadata from prisma/prisma to prisma/orm
  • update the manifest provenance guard and its tests

Validation

  • node --test scripts/validate-package-manifests.test.mjs
  • node scripts/validate-package-manifests.mjs
  • parsed all package manifests as JSON
  • git diff --check

Summary by CodeRabbit

  • Chores
    • Updated package repository metadata to reference the Prisma ORM repository.
    • Updated package manifest validation and its tests to recognize the new canonical repository URL.

@StevenMcClankerton
StevenMcClankerton requested a review from a team as a code owner August 26, 2026 15:22
@coderabbitai

coderabbitai Bot commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

@pkg-pr-new

pkg-pr-new Bot commented Aug 26, 2026

Copy link
Copy Markdown

Open in StackBlitz

@prisma/orm-extension-arktype-json

npm i https://pkg.pr.new/@prisma/orm-extension-arktype-json@30145

@prisma/orm-extension-middleware-cache

npm i https://pkg.pr.new/@prisma/orm-extension-middleware-cache@30145

@prisma/orm-extension-paradedb

npm i https://pkg.pr.new/@prisma/orm-extension-paradedb@30145

@prisma/orm-extension-pgvector

npm i https://pkg.pr.new/@prisma/orm-extension-pgvector@30145

@prisma/orm-extension-postgis

npm i https://pkg.pr.new/@prisma/orm-extension-postgis@30145

@prisma/orm-extension-supabase

npm i https://pkg.pr.new/@prisma/orm-extension-supabase@30145

@prisma/orm-family-mongo

npm i https://pkg.pr.new/@prisma/orm-family-mongo@30145

@prisma/orm-family-sql

npm i https://pkg.pr.new/@prisma/orm-family-sql@30145

@prisma/orm-framework

npm i https://pkg.pr.new/@prisma/orm-framework@30145

@prisma/orm-mongo

npm i https://pkg.pr.new/@prisma/orm-mongo@30145

@prisma/orm-postgres

npm i https://pkg.pr.new/@prisma/orm-postgres@30145

@prisma/orm-sqlite

npm i https://pkg.pr.new/@prisma/orm-sqlite@30145

@prisma/orm-target-mongo

npm i https://pkg.pr.new/@prisma/orm-target-mongo@30145

@prisma/orm-target-postgres

npm i https://pkg.pr.new/@prisma/orm-target-postgres@30145

@prisma/orm-target-sqlite

npm i https://pkg.pr.new/@prisma/orm-target-sqlite@30145

@prisma/orm-toolchain

npm i https://pkg.pr.new/@prisma/orm-toolchain@30145

commit: 5274c53

@github-actions

Copy link
Copy Markdown
Contributor

size-limit report 📦

Path Size
postgres / no-emit 174.86 KB (0%)
postgres / emit 152.08 KB (0%)
mongo / no-emit 101.09 KB (0%)
mongo / emit 90.95 KB (0%)
cf-worker / no-emit 198.74 KB (0%)
cf-worker / emit 173.36 KB (0%)

@SevInf
SevInf merged commit 007f39a into main Aug 26, 2026
19 of 20 checks passed
@SevInf
SevInf deleted the chore/update-npm-provenance-main branch August 26, 2026 15:39
Shgit29 pushed a commit to Shgit29/prisma that referenced this pull request Aug 31, 2026
…risma#30179)

## Linked issue

n/a — small change; fallout from the repository rename (prisma/prisma →
prisma/orm).

## Summary

The publish workflow's "Notify prisma-cli" step never reached its
consumer. It sent `event_type: family-published`, but prisma-cli's
`update-product-versions.yml` triggers on `product-published`, so the
auto-repin only ever ran from its daily scheduled backstop. The payload
also still named this repo `prisma/prisma`. The step now sends
`product-published` with `repo: prisma/orm`.

## Testing performed

- Verified the receiving side: `prisma/prisma-cli`
`.github/workflows/update-product-versions.yml` triggers on
`repository_dispatch: types: [product-published]` and reads nothing from
the payload, so the `repo` field is informational.
- The diff changes only characters inside an existing quoted scalar; no
YAML structure changed.

## Skill update

n/a — internal only (CI workflow; no user-facing surface).

## Checklist

- [x] All commits are signed off (`git commit -s`) per the
[DCO](../CONTRIBUTING.md#developer-certificate-of-origin-dco). The DCO
status check will block merge if any commit is missing a
`Signed-off-by:` trailer.
- [x] I read [CONTRIBUTING.md](../CONTRIBUTING.md) and the change is
scoped to one logical concern.
- [x] Tests are updated (n/a — CI workflow change, no test surface).
- [ ] The PR title is in `TML-NNNN: <sentence-case title>` form — no
Linear ticket exists for this rename fallout; the title follows the
repo's convention for such chores (cf. prisma#30145).
- [x] The **Skill update** section above is filled in.

## Notes for the reviewer

- The event-type mismatch predates the rename. prisma-cli's consumer
workflow was created on 2026-08-17 listening for `product-published`
(prisma/prisma-cli#192); this sender, added on 2026-08-13, was never
updated. The daily cron masked the dead letter — a lost dispatch delays
the repin by at most a day, which is why nothing visibly broke.
- Companion PRs update the other side of the rename: `prisma/orm` `v7`
branch (`github.repository` guards), `prisma/engines-wrapper` (workflow
dispatch target), and `prisma/prisma-engines` (Makefile clone URL).


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **Chores**
* Updated the publication notification event type to
`product-published`.
* Repository and version information in the notification remain
unchanged.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

Signed-off-by: Oleksii Orlenko <robot@aqrln.net>
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