From 2fb17071e4c8b5b9f116f49669c57944e1f44aee Mon Sep 17 00:00:00 2001 From: willbot Date: Mon, 14 Sep 2026 16:48:27 +0200 Subject: [PATCH] docs(oss): the notify example must use gh api -f, not -F gh api -F reads a value that starts with @ from a file, so '@prisma/composer-cli' fails to parse before any request is made. A product repository that copies the example verbatim never sends the dispatch (prisma/composer#295 did exactly that). -f sends the literal string. Signed-off-by: willbot Signed-off-by: Will Madden Co-Authored-By: Claude Fable 5.1 --- docs/oss/release-automation.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/oss/release-automation.md b/docs/oss/release-automation.md index 769c9e4b..ae4f9aec 100644 --- a/docs/oss/release-automation.md +++ b/docs/oss/release-automation.md @@ -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.