Skip to content

Fix trusted publishing repository metadata #1517

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sorenbs merged 1 commit into from
Jun 4, 2026
Merged

Fix trusted publishing repository metadata #1517

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions RELEASE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,8 @@ This repository supports two release paths. Both publish from `main`, use npm tr

Configure `@prisma/studio-core` in npm as a trusted publisher for the `prisma/studio` GitHub repository and the publish workflow. The workflow does not use `NPM_TOKEN`.

Keep `package.json` `repository.url` set to `https://github.com/prisma/studio`. npm validates that package metadata against the GitHub Actions provenance bundle during trusted publishing.

## Path 1: Changesets Release PR

Use this path for normal releases.
Expand Down
4 changes: 4 additions & 0 deletions package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,10 @@
"name": "@prisma/studio-core",
"version": "0.28.0",
"description": "Modular Prisma Studio components",
"repository": {
"type": "git",
"url": "https://github.com/prisma/studio"
},
"type": "module",
"sideEffects": false,
"exports": {
Expand Down