ci: fix the prisma-cli publish notification (event type, repo name) by tensordreams · Pull Request #30179 · prisma/orm · GitHub
Skip to content

ci: fix the prisma-cli publish notification (event type, repo name) - #30179

Merged
aqrln merged 1 commit into
mainfrom
ci-publish-notify-rename
Aug 31, 2026
Merged

ci: fix the prisma-cli publish notification (event type, repo name)#30179
aqrln merged 1 commit into
mainfrom
ci-publish-notify-rename

Conversation

@tensordreams

@tensordreams tensordreams commented Aug 31, 2026 •
edited by coderabbitai Bot
Loading

Copy link
Copy Markdown
Contributor

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

  • All commits are signed off (git commit -s) per the DCO. The DCO status check will block merge if any commit is missing a Signed-off-by: trailer.
  • I read CONTRIBUTING.md and the change is scoped to one logical concern.
  • 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. chore: update npm provenance repository #30145).
  • 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 (A release of the CLI depends only on released product versions 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).

Summary by CodeRabbit

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

@tensordreams
ci: fix the prisma-cli publish notification (event type, repo name)
ce64efa 
The notify step sent event_type family-published, which prisma-cli
does not listen for: its update-product-versions workflow triggers on
product-published. The payload also named this repo prisma/prisma, its
name before the rename to prisma/orm. Send product-published with
repo prisma/orm, so the notification reaches the repin workflow instead
of relying on its daily scheduled backstop.

Signed-off-by: Oleksii Orlenko <robot@aqrln.net>
@tensordreams
tensordreams requested a review from a team as a code owner August 31, 2026 14:43
@coderabbitai

coderabbitai Bot commented Aug 31, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

@tensordreams tensordreams mentioned this pull request Aug 31, 2026
Merged
@pkg-pr-new

pkg-pr-new Bot commented Aug 31, 2026

Copy link
Copy Markdown

Open in StackBlitz

@prisma/orm-extension-arktype-json

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

@prisma/orm-extension-middleware-cache

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

@prisma/orm-extension-paradedb

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

@prisma/orm-extension-pgvector

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

@prisma/orm-extension-postgis

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

@prisma/orm-extension-supabase

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

@prisma/orm-family-mongo

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

@prisma/orm-family-sql

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

@prisma/orm-framework

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

@prisma/orm-mongo

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

@prisma/orm-postgres

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

@prisma/orm-sqlite

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

@prisma/orm-target-mongo

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

@prisma/orm-target-postgres

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

@prisma/orm-target-sqlite

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

@prisma/orm-toolchain

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

commit: ce64efa

@github-actions

github-actions Bot commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

size-limit report 📦

Path Size
postgres / no-emit 174.89 KB (0%)
postgres / emit 152.03 KB (0%)
mongo / no-emit 101.09 KB (0%)
mongo / emit 90.95 KB (0%)
cf-worker / no-emit 198.77 KB (0%)
cf-worker / emit 173.31 KB (0%)

@aqrln
aqrln added this pull request to the merge queue Aug 31, 2026
Merged via the queue into main with commit 5e0f135 Aug 31, 2026
26 checks passed
@aqrln
aqrln deleted the ci-publish-notify-rename branch August 31, 2026 16:35
aqrln pushed a commit that referenced this pull request Sep 1, 2026
@tensordreams
ci: update github.repository checks for the rename to prisma/orm (#30180
9028ed8 
)

## Summary

The repository was renamed from prisma/prisma to prisma/orm, so
`github.repository == 'prisma/prisma'` is now always false. Two things
have been silently skipped on this branch since the rename:

- the eight BuildPulse upload steps in
`.github/workflows/test-template.yml`
- the benchmark job in `.github/workflows/benchmark.yml`

This PR updates those guards to `'prisma/orm'`. The guards keep their
purpose: forks still see a different `github.repository`, so they still
skip these steps.

Also updated, cosmetic only: the Slack release titles in `publish.yml`
and one comment in `v7-update-engines-version.yml`.

## Testing performed

- `grep -rP "prisma/prisma(?![-_A-Za-z])" .github/workflows/` finds no
remaining bare references. `@prisma/prisma-schema-wasm` and
`prisma/prisma-engines` references are intentionally untouched.
- The diff changes only string literals inside existing expressions and
one comment; no YAML structure changed.

## Related PRs

Companion rename fixes: #30179 (`main` publish notification),
prisma/engines-wrapper#539 (workflow dispatch target),
prisma/prisma-engines#5859 (Makefile clone URL).


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

## Summary by CodeRabbit

- **Chores**
  - Updated automated workflows to reference the current repository.
- Benchmarking and build metrics uploads now run under the correct
repository context.
  - Release notifications now identify the correct repository.
- Updated integration-testing workflow documentation to reflect the
current repository.

<!-- 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

Reviewers

@aqrln aqrln aqrln approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@tensordreams @aqrln