repository-dispatch
Utilities for working with dispatch events triggered by Vercel
by vercelTypeScript
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?v=4&s=144)
![vercel[bot]](https://avatars.githubusercontent.com/in/8329?v=4&s=144)
Commit activity
Last 12 weeks · 2 commits
Community health
3 of 6 standards met
62
✓README✓License✓Contributing○Code of Conduct○Issue Template○PR Template
Recent PRs & issues
Quiet · 1 in progress · Last activity 2mo ago
See all on GitHub →
I got this warning in my action run: Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: vercel/repository-dispatch/actions/status@v1.
SHA-pinning tools like pinact resolve the latest version for this repo as and pin its SHA because they fail to locate latest version. Consumers who manually start from a good pin get reverted to the non-functional state on the next update run. Suggested fix Cut a proper release from current that is reachable via a normal semver tag, and pinning tools resolve the correct . cc @tknickman
Repository dispatch success events can include deployment aliases, but the client payload type did not model that field. This PR updates the payload contract so consumers can read aliases in a typed way. Payload type update Added optional to in . Keeps backward compatibility by making the field optional. Documentation update Updated the package payload example in to include and show a success-state payload. Aligns docs with the event shape expected by consumers. Release metadata** Added a changeset for patch release.
Recent fixes
Summary GitHub Actions is deprecating Node 20 on runners starting June 2 (changelog). This PR upgrades the sub-action to use the runtime. Changes:** : → : → : add to the test matrix The and sub-actions are composite actions and are unaffected. The compiled dist output is unchanged — only the runtime declaration needed updating.
Hi, the repository-dispatch actions block us from enabling "Require actions to be pinned to a full-length commit SHA" (see https://github.blog/changelog/2025-08-15-github-actions-policy-now-supports-blocking-and-sha-pinning-actions/) because they internally don't use version pinning. e.g. here: https://github.com/vercel/repository-dispatch/blob/main/actions/checkout/action.yaml#L46 It would be great to use full-length SHAs in this repository to unblock us from enabling this enforcement. I'm not sure if it provides any real security benefit to version-pin GitHub created actions but they can't be excluded from this rule unfortunately. cc @tknickman
Structured data for AI agents
Repository: vercel/repository-dispatch. Description: Utilities for working with dispatch events triggered by Vercel Stars: 13, Forks: 7. Primary language: TypeScript. Languages: TypeScript (94%), JavaScript (6%). License: MIT. Homepage: https://repository-dispatch-smoke-example.vercel.app Latest release: @vercel/repository-dispatch@0.1.0 (1y ago). Open PRs: 1, open issues: 3. Last activity: 2mo ago. Community health: 62%. Top contributors: tknickman, prisubs, vercel-release-bot, github-actions[bot], vercel[bot].