Provider changes

By Ohad Krispin, founder of VibeRaven · LinkedIn

`changes` compares a dated list of provider changes, such as Supabase Data API grants or Vercel dropping Node 20, with your repository, and says which ones affect it, with the file and line. A change with no signal in the repo is reported as not checked, never as safe.

npx -y viberaven@1.7.8 changes

Run it in the project root. It reads files only and needs no account. Or ask your coding agent to "run npx -y viberaven changes and update what it lists".

Read the result

Each change gets one of four statuses, then the evidence, the fix and the official source. This is part of a real run:

Provider changes vs this repo (pack 1.1.0, reviewed 2026-11-02)

AFFECTED            vercel: vercel-node20-to24 (2026-10-01)
  engines.node "20.x" allows Node 20 at most; Vercel stopped building with Node 20, and engines overrides the Project Settings.
  - package.json:6: engines.node is "20.x"
  Fix: Change a Node 20 engines.node pin to 24.x, or select 24.x in Project Settings when engines is absent; ...
  Source: https://vercel.com/changelog/node-js-20-is-being-deprecated

not affected        stripe: stripe-endive-payment-method-types (2026-09-30)
  No Checkout Session, PaymentIntent or SetupIntent call sends payment_method_types.

3 affected, 2 to review, out of 12 changes.

AFFECTED: The repo shows the change applies, with the file and line. Fix it before the next deploy.
REVIEW: The repo shows a signal that may apply. Check it yourself, for example which version the lockfile installs, or when a legacy key stops working.
not affected: The repo has the provider, and none of the affected code.
not checked by repo: No sign of that provider in the repo. That is not the same as safe.

What it covers

Pack 1.1.0, reviewed on November 2, 2026, has 12 dated changes:

Provider changes in viberaven 1.7.8
Id	Provider	Date
`supabase-explicit-data-api-grants`	Supabase	2026-10-30
`supabase-publishable-secret-api-keys`	Supabase	2026-10-30
`vercel-node20-to24`	Vercel	2026-10-01
`next-security-2026-10-14`	Next.js	2026-10-14
`next-cache-components-suspense`	Next.js	2026-10-06
`stripe-endive-payment-method-types`	Stripe	2026-09-30
`clerk-production-instance-keys`	Clerk	2026-10-30
`lovable-test-live-retired`	Lovable	2026-10-23
`lovable-ai-gemini-retirements`	Lovable	2026-11-19
`railway-config-as-code-retirement`	Railway	2026-12-01
`openai-model-shutdowns-2026`	OpenAI	2026-12-11
`anthropic-claude-model-retirements`	Anthropic	2026-11-30

The date is when the change takes effect or was announced. A newer CLI version may carry a newer pack.

Flags

[path]: The folder to read. Defaults to the current folder.
--json: One JSON object with a changes array: id, provider, date, status, why, evidence (file, line, detail), fix and officialSource.
--strict: Exit 1 when a change affects the repo. Without it, changes exits 0.

The flags are switches without values: --strict=true is an error.

In the check

check lists the affected changes too, under Provider changes that affect this repo, and points to changes for the fix and source of each.

Limits

It reads repository files only. Live provider settings, dashboards and deployed runtimes are not checked.
Not affected by these changes is not the same as safe.
The hosted MCP tool recent_provider_changes returns the same dated changes for an agent that cannot run the CLI.

Checked

Checked on November 3, 2026, against the published viberaven 1.7.8, with a real run on a small Next.js + Supabase + Stripe fixture repo.