Skip to content

docs(oss): the notify example must use gh api -f, not -F #269

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
wmadden-electric merged 1 commit into from
Sep 14, 2026
Merged

docs(oss): the notify example must use gh api -f, not -F #269

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
4 changes: 2 additions & 2 deletions docs/oss/release-automation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,8 +56,8 @@ A step in the publish workflow, immediately after its publish step and keyed on
run: |
gh api repos/prisma/prisma-cli/dispatches \
-f event_type=product-published \
-F 'client_payload[package]=@prisma/composer-cli' \
-F "client_payload[version]=$VERSION"
-f 'client_payload[package]=@prisma/composer-cli' \
-f "client_payload[version]=$VERSION"
```

The payload is informational — this repository always re-reads the registry rather than trusting the event, so a malformed or replayed event cannot pin a version that does not exist.
Expand Down
Loading