You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a developer who uses Vercel's SDK or deploys functions on Vercel, I want patch-it to watch Vercel's other official sources, not only the one it reads today, so changes in those also reach my code as a fix.
Missing sources
Proposed; check each before writing it (verify, don't guess; leave TBD if unknown). Ids follow the provider/source form (I19.2).
vercel/sdk · kind changelog · layer sdk · vercel/sdk releases: breaking SDK changes (the API spec is already watched)
vercel/sdk-surface · kind apisurface (kind not built yet: waits for I19.10) · layer sdk · @vercel/sdk on npm (.d.ts): removed methods between releases
vercel/runtimes · kind notices · layer runtime · Vercel's changelog or docs on Node.js runtime deprecations: runtime versions retired on a date
Subtasks
For each source: link, date checked, why it's the best source and a short quote, in providers/vercel.md under Why this source
One source per PR, registered under the existing Vercel provider
Saved copies in testdata/ (row in testdata/README.md: URL, date fetched, license, quote), a golden file, and one drop test
The source lists its versions (I19.8) where its kind supports it
make check passes
Acceptance criteria
Each new source emits events with source_url and an exact source_excerpt
The drop test produces no event
The provider page lists every source with its date checked
Activity