Skip to content

chore(deps-dev): bump the dev-tooling group across 1 directory with 7 updates - #26

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/dev-tooling-e7be97e4fe
Closed

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/dev-tooling-e7be97e4fe

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 7, 2026 •

Copy link
Copy Markdown
Contributor

Bumps the dev-tooling group with 7 updates in the / directory:

Package From To
@cloudflare/vite-plugin 1.62.3 1.67.0
@vitejs/plugin-react 6.0.5 6.2.1
oxlint 1.78.0 1.92.0
supabase 2.118.0 3.0.0
tailwindcss 3.4.19 4.3.5
vite 8.2.1 8.3.6
wrangler 4.145.0 4.156.1

Updates @cloudflare/vite-plugin from 1.62.3 to 1.67.0

Changelog

Sourced from @​cloudflare/vite-plugin's changelog.

1.67.0

Minor Changes

  • #16543 0489cda Thanks @​petebacondarwin! - Validate asset ignore files and update local Flagship support

    Upgrade Miniflare to 5.20261023.2-beta and Wrangler to 4.155.0. Builds and asset manifest generation now reject .assetsignore files with invalid UTF-8 or null characters instead of silently ignoring their patterns. The Local Explorer also supports Flagship management by app ID, and local flag evaluations retain metadata.

    Miniflare also waits for temporary file cleanup before disposal completes, so closing or restarting a Vite dev server finishes cleanup before returning.

  • #16579 e696113 Thanks @​petebacondarwin! - Support remote Analytics Engine bindings in Vite plugin v1

    Set remote: true on an analytics_engine_datasets entry in wrangler.jsonc to send writeDataPoint() calls from local development and preview to the real dataset.

Patch Changes

  • #16578 2eae147 Thanks @​petebacondarwin! - Close Vite HMR WebSocket upgrades when Vite WebSockets are disabled

    Previously, server.ws: false left the browser's raw upgrade socket pending because no Vite handler claimed it. Worker and Sandbox WebSocket forwarding remains unchanged.

  • #16639 a6f98d0 Thanks @​petebacondarwin! - Update the v1 local runtime to workerd 1.20261101.1

    Upgrade Miniflare to 5.20261101.0-beta with matching Wrangler and shared SDK dependencies. Local development and preview use the November 1 runtime, and Workers without an explicit compatibility date default to 2026-11-01. Update Workers types to match the runtime.

1.66.0

Minor Changes

  • #16539 046db08 Thanks @​petebacondarwin! - Update the development registry to use the canonical Cloudflare path

    Upgrade Miniflare to 5.20261023.1-beta and Wrangler to 4.154.0. Vite plugin v1 now uses CLOUDFLARE_DEV_REGISTRY_PATH or <Cloudflare config directory>/dev-registry/v5 for Worker discovery. MINIFLARE_REGISTRY_PATH is no longer read. When mixing Vite and Wrangler development sessions, set the same CLOUDFLARE_DEV_REGISTRY_PATH for both because Wrangler retains its legacy default.

  • #16407 9ec1101 Thanks @​petebacondarwin! - Support remote Hyperdrive bindings in Vite plugin v1 development and preview

    Set remote: true on a Hyperdrive binding in wrangler.jsonc to connect to its deployed configuration without a local database connection string. The retained remote proxy exposes the binding's connection string and socket streams, and remote session cleanup preserves startup errors and shares one disposal attempt.

Patch Changes

  • #16542 ef573d4 Thanks @​petebacondarwin! - Preserve machine-readable error properties from remote bindings

    Enable enhanced error serialization on the remote proxy Worker used by Vite plugin v1. Combined with Miniflare 5.20261023.1-beta, remote binding errors retain properties such as code and numericCode so Worker code can handle them without parsing error messages.

  • #16480 ccaa34a Thanks @​petebacondarwin! - Prevent malformed token-exchange responses from crashing remote binding startup

    Update the Undici dependency bundled from the retained remote-bindings package to 7.30.1. Responses with excessive content encodings now reject without a later unhandled stream error when the server closes the connection early.

  • #16502 6f2eda1 Thanks @​petebacondarwin! - Update the retained asset configuration validator to Zod 4.6.6

    The Vite plugin validates _headers and _redirects through its private workers-shared package. Update that bundled copy to address excessive memory consumption when validating oversized collections.

... (truncated)

Commits
  • 7a293fc [vite-plugin] Version v1 maintenance release (#16600)
  • a6f98d0 [vite-plugin] Update v1 to the November 1 runtime (#16639)
  • 2eae147 [vite-plugin] Close disabled v1 HMR WebSocket upgrades (#16578)
  • 0489cda [vite-plugin] Update v1 asset validation, Flagship and disposal runtime (#16543)
  • ae80956 [vite-plugin] Version v1 maintenance release (#16544)
  • 046db08 [vite-plugin] Update v1 development registry and runtime (#16539)
  • 79678c4 [vite-plugin] Update v1 to the October 23 runtime (#16444)
  • d3b872f [vite-plugin] Route v1 DevTools WebSocket upgrades explicitly (#16540)
  • 436fa9a [vite-plugin] Preserve WebSockets owned by other v1 listeners (#16504)
  • ca116f9 [vite-plugin] Clear v1 Worker exports between dev servers (#16503)
  • Additional commits viewable in compare view

Updates @vitejs/plugin-react from 6.0.5 to 6.2.1

Release notes

Sourced from @​vitejs/plugin-react's releases.

plugin-react@6.2.1

Fix refreshInclude and refreshExclude options not working (#1543)

Fix mistake from #1516

plugin-react@6.2.0

Add refreshInclude and refreshExclude options (#1516)

Add refreshInclude and refreshExclude options to skip fast refresh for certain files that won't run in the browser.

Expand oxc-transform-react peer dependency range (#1540)

The peer dependency version range for oxc-transform-react was expanded from ^0.152.0 to >=0.152.0 <0.157.0.

Expand @rolldown/plugin-babel peer dependency range (#1541)

The peer dependency version range for @rolldown/plugin-babel was expanded from ^0.1.7 || ^0.2.0 to ^0.1.7 || ^0.2.0 || ^0.3.0.

plugin-react@6.1.2

Fix HMR for compound components (#1484)

Adding or removing a component from a compound component was not handled, creating stale updates. Doing this now triggers hmr invalidate on the file and propagates the invalidation to importers.

Fix compiler.logDiagnostics option not working (#1483)

With oxc-transform-react >= 0.148, the logDiagnostics was not working. This version fixes it and requires oxc-transform-react >= 0.152 as a peer dependency if you are using the compiler option. compiler.logDiagnostics option is now deprecated and should be swapped for the builtin compiler.reportDiagnostics.

Disable refresh for non-jsx with compiler enabled (fix #1478) (#1485)

When the compiler was enabled, TS files could trigger fast refresh which would cause runtime errors. The logic now follows what the builtin oxc plugin in Vite does.

plugin-react@6.1.1

Add compiler.logDiagnostics option

Recoverable React Compiler diagnostics are no longer logged by default. Set compiler.logDiagnostics to true to log them through Vite. Fatal diagnostics are always logged and fail the transform.

Respect environment sourcemap option for React Compiler transform when builder.sharedPlugins is enabled (#1439)

The React Compiler transform was using the top-level sourcemap option instead of the environment sourcemap option. This caused a problem when the experimental builder.sharedPlugins was enabled.

plugin-react@6.1.0

Add experimental native React Compiler support (#1419)

Add experimental native React Compiler support.

You can use it by installing oxc-transform-react and enabling it via the compiler option:

npm install -D oxc-transform-react
</tr></table> 

... (truncated)

Changelog

Sourced from @​vitejs/plugin-react's changelog.

6.2.1 (2026-11-02)

Fix refreshInclude and refreshExclude options not working (#1543)

Fix mistake from #1516

6.2.0 (2026-11-02)

Add refreshInclude and refreshExclude options (#1516)

Add refreshInclude and refreshExclude options to skip fast refresh for certain files that won't run in the browser.

Expand oxc-transform-react peer dependency range (#1540)

The peer dependency version range for oxc-transform-react was expanded from ^0.152.0 to >=0.152.0 <0.157.0.

Expand @rolldown/plugin-babel peer dependency range (#1541)

The peer dependency version range for @rolldown/plugin-babel was expanded from ^0.1.7 || ^0.2.0 to ^0.1.7 || ^0.2.0 || ^0.3.0.

6.1.2 (2026-10-05)

Fix HMR for compound components (#1484)

Adding or removing a component from a compound component was not handled, creating stale updates. Doing this now triggers hmr invalidate on the file and propagates the invalidation to importers.

Fix compiler.logDiagnostics option not working (#1483)

With oxc-transform-react >= 0.148, the logDiagnostics was not working. This version fixes it and requires oxc-transform-react >= 0.152 as a peer dependency if you are using the compiler option. compiler.logDiagnostics option is now deprecated and should be swapped for the builtin compiler.reportDiagnostics.

Disable refresh for non-jsx with compiler enabled (fix #1478) (#1485)

When the compiler was enabled, TS files could trigger fast refresh which would cause runtime errors. The logic now follows what the builtin oxc plugin in Vite does.

6.1.1 (2026-08-28)

Add compiler.logDiagnostics option

Recoverable React Compiler diagnostics are no longer logged by default. Set compiler.logDiagnostics to true to log them through Vite. Fatal diagnostics are always logged and fail the transform.

Respect environment sourcemap option for React Compiler transform when builder.sharedPlugins is enabled (#1439)

The React Compiler transform was using the top-level sourcemap option instead of the environment sourcemap option. This caused a problem when the experimental builder.sharedPlugins was enabled.

6.1.0 (2026-08-19)

Add experimental native React Compiler support (#1419)

Add experimental native React Compiler support.

... (truncated)

Commits
  • 29efd1c release: plugin-react@6.2.1 (#1544)
  • 22079fa fix(plugin-react): fix new refreshInclude option (#1543)
  • d0f7234 release: plugin-react@6.2.0 (#1542)
  • 186d1e8 feat(plugin-react): expand @rolldown/plugin-babel peer dep range (#1541)
  • a554a33 feat(plugin-react): expand oxc-transform-react peer dep range (#1540)
  • ef758ba fix(deps): update all non-major dependencies (#1531)
  • 304a92a feat(plugin-react): add refreshInclude and refreshExclude options (#1516)
  • b3e9835 fix(deps): update all non-major dependencies (#1517)
  • 65a1dd5 fix(deps): update react 19.3.1 (#1509)
  • 443be64 chore(deps): update dependency typescript to v7 (#1422)
  • Additional commits viewable in compare view

Updates oxlint from 1.78.0 to 1.92.0

Release notes

Sourced from oxlint's releases.

oxlint v1.92.0

🚀 Features

  • 4a52ba2 oxlint: Discover tsrs for type-aware linting (#28751) (camc314)
  • b7d2c75 linter/eslint/no-redeclare: Add ignoreDeclarationMerge option (#28816) (Cam McHenry)

🐛 Bug Fixes

  • fa66fde oxlint,oxfmt: Resolve Vite+ config root from the config file directory (#28801) (MK (fengmk2))
  • 2091564 linter/jsdoc/require-param: Ignore enclosing function JSDoc (#28866) (camc314)
  • c6ec50b linter/react/only-export-components: Classify JSX values as non-components (#28761) (camc314)
  • 3c051ab linter/vitest/prefer-called-exactly-once-with: Preserve neighboring code in autofix (#28864) (camc314)
  • 674b962 linter/eslint/no-misleading-character-class: Use lazy regex for combining marks (#28822) (Sysix)
  • 838d339 linter/vitest/prefer-called-exactly-once-with: Avoid panic on non-ASCII text (#28850) (YT)
  • 8d24c26 linter/jsx-a11y/aria-role: Allow role={undefined} (#28804) (Abhay Godavarthy)
  • a7143bf linter/eslint/no-restricted-imports: Respect allowTypeImports correctly for empty patterns (#28842) (Cam McHenry)
  • 3d3a6f4 react-compiler: Ignore callback-local reassignments (#28820) (camc314)
  • 0cc6515 linter/unicorn/prefer-type-error: Report throws in unbraced if branches (#28819) (camc314)
  • ae43c80 linter/unicorn/prefer-single-call: Remove duplicate fix status (#28763) (Mikhail Baev)
  • a8a621a linter/eslint/no-fallthrough: Ignore unreachable exits from infinite loops (#28755) (camc314)
  • 7a17a80 linter/eslint/prefer-spread: Report calls on non-member expressions (#28753) (camc314)
  • 28442f7 oxlint: Prevent --init from overwriting existing configs (#28754) (camc314)
  • 0ae350d linter/unicorn/no-zero-fractions: Preserve exponent case (#28752) (camc314)
  • b5b3f3f linter/eslint/no-misleading-character-class: Detect more combining characters (#28733) (Sysix)

⚡ Performance

  • 74d50c1 linter: Overlap import graph batches instead of polling on a pool worker (#28323) (Dunqing)

oxlint v1.91.0

🚀 Features

  • 004647a track_memory_allocs: Add allocation tracking for linter rules (#28470) (Cam McHenry)
  • 419c1b0 linter: Add allow and allowPattern options to react/capitalized-calls (Christian Vuerings)

🐛 Bug Fixes

  • a205cd3 linter/eslint/no-control-regex: Detect raw control characters (#28548) (camc314)
  • 7c65777 linter/unicorn/prefer-global-this: Align typeof and worker API handling (#28549) (camc314)
  • 987d5f1 linter/unicorn/no-invalid-fetch-options: Avoid treating unknown methods as GET (#28547) (camc314)
  • e234dc8 linter/unicorn/no-useless-error-capture-stack-trace: Move to suspicious category (#28545) (camc314)
  • b3dc411 linter/typescript/no-non-null-asserted-nullish-coalescing: Move to suspicious category (#28546) (camc314)
  • cb64638 regular_expression: Reject incomplete Unicode atom escapes (#28448) (Boshen)
  • c67167e linter: Only run React Compiler rules on files with top-level components or hooks (Boshen)
  • 4c9d5aa linter: Treat Reanimated shared values as ref-like in React Compiler rules (Boshen)
  • 61fe2af linter/react: Ignore impure calls in async components in react/purity (Rahul Kashyap)
  • ed7df7d ast/estree: Include comments in TS Program span (#28326) (camc314)
  • 31cbe37 linter: Make gitlab fingerprints unique per diagnostic (#28307) (camc314)

⚡ Performance

... (truncated)

Changelog

Sourced from oxlint's changelog.

[1.92.0] - 2026-11-06

🚀 Features

  • b7d2c75 linter/eslint/no-redeclare: Add ignoreDeclarationMerge option (#28816) (Cam McHenry)

[1.91.0] - 2026-11-02

🚀 Features

  • 419c1b0 linter: Add allow and allowPattern options to react/capitalized-calls (Christian Vuerings)

[1.90.0] - 2026-10-27

🚀 Features

  • 831cdf1 oxlint: Require mininum oxlint-tsgolint version v7.0.2005 (#28118) (camc314)
  • d1b00f4 linter/typescript: Implement no-unsafe-enum-assignment rule (#28117) (camc314)
  • 165c91f linter/typescript/await-thenable: Support allowMixedPromiseArrays option (#28116) (camc314)

[1.89.0] - 2026-10-19

🐛 Bug Fixes

  • 9a424c2 oxlint,oxfmt: Correct Node.js TypeScript support range (#27699) (camc314)

[1.88.0] - 2026-10-13

🚀 Features

  • 3c361a7 linter/unicorn/prefer-query-selector: Add allowWithVariables option (#27346) (Mikhail Baev)

[1.86.0] - 2026-09-28

🚀 Features

  • 9d80eed linter/react/only-export-components: Support allowCompoundComponents (#27117) (Kuroda Kayn)
  • e05b155 linter: Add typescript/no-generated-empty-object-type (#26958) (camc314)

[1.82.0] - 2026-09-07

🚀 Features

  • 6a0e19c linter/eslint/no-unmodified-loop-condition: Support checkConditionalExpressions option (#26249) (camc314)

[1.81.0] - 2026-08-31

📚 Documentation

  • d5be037 linter/typescript/switch-exhaustiveness-check: Clarify default case comment pattern (#26100) (camc314)

... (truncated)

Commits
  • 29daf90 release(apps): oxlint v1.92.0 && oxfmt v0.77.0 (#28906)
  • b7d2c75 feat(linter/eslint/no-redeclare): add ignoreDeclarationMerge option (#28816)
  • f3fcdcc release(apps): oxlint v1.91.0 && oxfmt v0.76.0 (#28718)
  • 419c1b0 feat(linter): add allow and allowPattern options to react/capitalized-calls
  • 9b6fff4 release(apps): oxlint v1.90.0 && oxfmt v0.75.0 (#28191)
  • 831cdf1 feat(oxlint): require mininum oxlint-tsgolint version v7.0.2005 (#28118)
  • d1b00f4 feat(linter/typescript): implement no-unsafe-enum-assignment rule (#28117)
  • 165c91f feat(linter/typescript/await-thenable): support allowMixedPromiseArrays opt...
  • 07ed78f release(apps): oxlint v1.89.0 && oxfmt v0.74.0 (#27961)
  • 9a424c2 fix(oxlint,oxfmt): correct Node.js TypeScript support range (#27699)
  • Additional commits viewable in compare view

Updates supabase from 2.118.0 to 3.0.0

Release notes

Sourced from supabase's releases.

v3.0.0

Supabase CLI v3.0.0 — 2026-11-02

v3 is a major release. Commands that can run locally now target your local stack by default, one --remote flag replaces --linked, --project-ref and --db-url, and every change to a hosted project asks for confirmation (or --yes in CI). Flags and SUPABASE_* environment variables now override config.toml, and deprecated commands, flags, config keys and the bundled supabase-go binary are gone. Read the breaking changes before you upgrade CI.

The v2 to v3 migration guide walks through each change.

⚠️ Upgrading an older project? Rename [inbucket] to [local_smtp] first. v3 can't load a supabase/config.toml that still has an [inbucket] section, which supabase init wrote before v2.108.0, so start, stop, status and the db commands fail with [inbucket] in supabase/config.toml is no longer supported. Rename the section, and any [remotes.<name>.inbucket] block; the keys inside don't change. v2.108.0 and later already read [local_smtp], so you can rename it before you upgrade. See Rename [inbucket] to [local_smtp].

Try the experimental local stack. Each project, worktree or agent gets its own local Supabase that starts in seconds, on Docker or Podman, or with no container engine at all through supabase start --runtime native. Start a new project with SUPABASE_EXPERIMENTAL_STACK=1 supabase init; for an existing one, follow the setup steps in the blog post. The multiple local projects guide covers listing, stopping and removing projects. It's experimental, so its flags and output can still change.

⚠️ Breaking changes

Local by default, one --remote flag

  • db push, db pull, db dump, migration fetch/list/repair, inspect db *, inspect report, gen types and storage ls/cp/mv/rm target the local stack when you pass no target. Add --remote for the linked project, --remote=<ref> for another project, --remote=<branch> for a branch of the linked project, or --remote=<postgres-url> for a database URL. SUPABASE_PROJECT_ID on its own no longer selects a hosted project; it only says which project bare --remote means. (#7188)
  • --linked, --project-ref, --db-url and gen types --project-id are deprecated. They still work, print a warning naming the --remote form, and are hidden from help. --local does nothing and warns. None of them can be combined with --remote=<value>. (#7188)
  • gen types with no target generates from the local database instead of opening a project picker. db schema declarative sync with no declarative files generates them from the local database; run supabase db schema declarative generate --remote first to start from the linked project. (#7188)
  • --remote <word> after a command that takes an operand fails with a "did you mean" error when the word looks like a branch name or project ref. Put the operand first (supabase db pull add_profiles --remote) or use --remote=<branch>. (#7188)
  • db diff rejects --remote together with --from/--to (use --from=remote or --to=remote), db query rejects SQL passed both as an argument and with --file, and an empty --project-ref= is now an error. Bare --remote in an unlinked checkout opens the project picker in an interactive terminal. (#7188)

Every hosted change needs your consent

  • Every command that changes a hosted project asks first, and fails unattended unless you pass --yes. Non-interactive, JSON, stream-json, agent and -o json|yaml|toml|env runs fail with HostedMutationConsentRequiredError. This includes db push, db pull when it updates the remote migration history, pull (except --dry-run), functions deploy/delete, secrets set/unset, config push, branches changes, backups restore, project and org create/delete, and the project settings commands. migration up/down/squash/repair, db reset, test db, db query, seed buckets and storage cp/mv/rm need it against a hosted target; db query --read-only doesn't. The migration guide has the full list. (#7188)
  • The default answer is No. Pressing Enter now declines db push, deploys, secrets changes and migration history updates. Only projects, branches, orgs and domains create, and bootstrap, default to Yes. (#7188)
  • A y piped on stdin no longer confirms, and SUPABASE_YES in a .env file no longer counts. When an env file in the working directory defines SUPABASE_YES, a shell-exported one doesn't count either. Use --yes. (#7188)
  • secrets unset defaults to No and needs --all to remove every secret. Running it with no secret names now fails. (#7172)
  • Declining fails with HostedMutationDeclinedError, replacing the per-command cancelled error codes. Declining db pull or pull writes no files. (#7188)
  • db push, hosted db reset, config push and functions deploy --prune ask one combined question, and --prune now runs even when every function is up to date. Removing network bans automatically while connecting now needs --yes. migration down and migration repair --all on the local database no longer prompt. (#7188)
  • Commands that resolve a target print Target: … once on stderr. JSON object results and error envelopes gain a target object; db reset's target changes from a string to that object, and config push JSON drops declined_addons and its skipped status. (#7188)

Flags and env vars override config

  • Every value now resolves as flag > shell environment > project env files > config.json/config.toml > default, and that includes a matched [remotes.<name>] block. Project env files are .env.<SUPABASE_ENV>.local, .env.local, .env.<SUPABASE_ENV> and .env, in supabase/ and then the project root. SUPABASE_ENV defaults to development. (#7074)
  • If you deploy with [remotes.*] blocks, audit the SUPABASE_* variables in CI and in your env files. They now beat the block, and config push pushes them (labelled per value; config diff shows the same). Set SUPABASE_ENV in CI so .env.development doesn't apply. (#7074)
  • Without a project_id in config.toml, local containers and volumes are named after the project folder, not the project ref. Run supabase stop before upgrading, or set project_id. (#7074)
  • An invalid config value or SUPABASE_* variable (for example SUPABASE_STUDIO_PORT=abc) now fails every command that loads config with CliConfigValueError. Boolean variables accept only 1/t/true and 0/f/false (with T, True, TRUE, F, False, FALSE). (#7074)
  • Seeding a project matched by a [remotes.*] block asks first unless the block sets db.seed.enabled = true. SUPABASE_DB_PASSWORD is no longer sent to a project other than the linked one, and --password with a local or URL target exits 1. (#7074)
  • Without --workdir, the nearest directory with supabase/config.toml or supabase/config.json wins. supabase link --password is ignored, ports with a leading zero are rejected, and MigrationPasswordFlagsError is now DbPasswordFlagsError. (#7074)

Removed commands, flags and config

Each removed command or flag exits 1 and prints its replacement. (#6609, #7109, #7116, #7176)

Removed Use instead
db remote commit db pull
db remote changes db diff --remote
db branch create/delete/list/switch branches for hosted preview branches
gen keys projects api-keys

... (truncated)

Changelog

Sourced from supabase's changelog.

Release Process

This document is the operational playbook for releasing the Supabase CLI TypeScript build. It covers three environments ("rings"):

  1. Ring 1 — Local Verdaccio. Fastest feedback loop. Build and install the CLI from a local npm registry on your own machine. No network side-effects; no repo pushes.
  2. Ring 2 — User-owned PoC repos. End-to-end validation through the exact same Homebrew / Scoop / GitHub-Release code paths production uses, but pointed at a reviewer's own GitHub account and a non-supabase artifact name. This is how ADR 0011 gates 2 and 3 are validated without risking the real production channels.
  3. Ring 3 — Production. The real supabase npm package + supabase/homebrew-tap + supabase/scoop-bucket + GitHub Releases on supabase/cli. Driven by GitHub Actions (release.yml, which dispatches four channels — beta, stable, next, maintenance — into the shared release-shared.yml).
flowchart LR
    local["Ring 1: Local Verdaccio<br/>pnpm cli-release"]
    poc["Ring 2: User-owned PoC repos<br/>avallete/supabase-cli-release-poc<br/>avallete/homebrew-supabase-shim-poc<br/>avallete/scoop-bucket<br/>--name supabase-shim-poc"]
    prod["Ring 3: Production<br/>supabase/cli<br/>supabase/homebrew-tap<br/>supabase/scoop-bucket<br/>(default name: supabase)"]
local --&gt; poc --&gt; prod

Loading

Move outward one ring at a time. Only promote to production after Ring 2 has exercised the full channel end-to-end on a fresh machine.

See ADR 0011 for the decision record behind this process (why Bun SFE, why npm optionalDependencies, why nfpm, why no hosted apt/rpm repo, why unsigned).


Ring 1 — Local Verdaccio

Use this loop while iterating on build scripts, the Node shim, or anything that changes what gets packed into supabase or @supabase/cli-<platform>. It installs the CLI into a local npm registry and lets you npx --registry http://localhost:4873 supabase as if you'd installed from npm.

Start the registry in one terminal:

pnpm local-registry

Publish the CLI into it from another terminal (current platform only, faster than a cross-platform build):

pnpm cli-release

Test it:

npx --registry http://localhost:4873 supabase@<printed-version> --version

[tools/release/local-release.ts](https://github.com/supabase/cli/blob/develop/tools/release/local-release.ts) does the heavy lifting: it builds the platform SFE and the umbrella supabase package, materialises them in a tmp dir (so no workspace package.json is modified), and publishes both to Verdaccio. The cleanup is automatic even on failure.

This is the right ring for:

  • Debugging the Node shim ([apps/cli/src/shared/cli/bin.ts](https://github.com/supabase/cli/blob/develop/apps/cli/src/shared/cli/bin.ts)) — which platform package gets resolved, execFileSync behaviour.

... (truncated)

Commits
  • c4ffa9c chore(stack): bump storage to v1.88.0-r0 (#7436)
  • a728de0 chore(stack): bump studio to 2026.11.02-sha-a05e7ec-r0 (#7432)
  • f4dafcd ci(cli): add a full benchmark for integration-heavy commands (#7412)
  • c6b9e5a chore(stack): bump realtime to v2.151.3-r0 (#7431)
  • e365ad6 chore(stack): bump postgres to 15.19.0.016-r0 (#7425)
  • 1a6eb19 chore(stack): bump postgres to 15.19.0.014-r0 (#7423)
  • 4581e0b ci(release): wait for platform packages before publishing the umbrella (#7417)
  • 140725a chore(stack): bump storage to v1.87.2-r0 (#7419)
  • e713e69 test(cli): cover the remaining test files with effect lint (CLI-2898) (#7414)
  • 94511ff chore(stack): bump realtime to v2.150.2-r0 (#7420)
  • Additional commits viewable in compare view

Updates tailwindcss from 3.4.19 to 4.3.5

Release notes

Sourced from tailwindcss's releases.

v4.3.5

Fixed

  • Canonicalization: improve performance in projects with many functional variant values (e.g. a matchVariant plugin with thousands of values) (#20663)
  • Don't crash or create a fallback with the wrong color for a color-mix(…) without a color interpolation method (e.g. color-mix(var(--color-red-500)) or color-mix(currentcolor 50%, transparent)) (#20658, #20666)
  • Ensure @tailwindcss/oxide-wasm32-wasi loads instead of hanging forever (e.g. with NAPI_RS_FORCE_WASI=error or in WebContainers) (#20667)
  • Remove as: '*.css' from the @tailwindcss/turbopack setup in its README, because it breaks CSS modules (#20660)
  • Ignore <!-- and --> between top-level rules in CSS instead of throwing or swallowing the next rule (e.g. a { color: red } --> b { color: blue }) (#20665)
  • Ensure @tailwindcss/oxide-wasm32-wasi detects changed and new source files after the first scan (e.g. in WebContainers) (#20487)
  • Prevent type errors with skipLibCheck: false caused by imports of unshipped modules in the @tailwindcss/node type declarations (#20632)

v4.3.4

Added

  • Add @tailwindcss/turbopack, a Turbopack loader for using Tailwind CSS with Next.js (#20367)

Fixed

  • Ensure watch mode detects changes to symlinked @source files whose real paths aren't otherwise scanned (#20356)
  • Ensure variants using @scope wrap generated utilities instead of nesting inside them (#20369)
  • Ensure nested @scope rules preserve their scoping semantics when flattened (#20369)
  • Preserve declarations directly inside @scope by wrapping them in :where(:scope) (#20369)
  • Ensure generated utilities include a space in empty var() fallbacks (e.g. var(--tw-blur,) → var(--tw-blur, )) (#20373)
  • Canonicalization: convert arbitrary breakpoint and container query variants to named equivalents (e.g. max-[64rem]:flex → max-lg:flex) (#20380)
  • Prevent @tailwindcss/vite from crashing on every edit under Vite's experimental bundledDev mode (#20379)
  • Ensure @tailwindcss/oxide falls back to WASM on platforms without native bindings (@tailwindcss/oxide-wasm32-wasi now installs on all platforms, but only loads when no native binding is available) (#20383)
  • Extract class candidates from Ruby %w and %W literals using angle brackets or custom delimiters (e.g. %w<flex>, %w|flex|), including in Slim and Haml templates (#20387)
  • Preserve whitespace in --default(…) values in functional @utility definitions (e.g. --default(box alphabetic) no longer becomes boxalphabetic) (#20392)
  • Ensure automatic source detection respects negation-based .gitignore files (e.g. /* followed by !/… patterns) (#20397)
  • Ensure root theme('…') namespace lookups in JavaScript plugins and config files return the full namespace object instead of the value of its DEFAULT key (#20399)
  • Skip ignored directories when generating watch globs instead of walking their contents on every rebuild (#20408)
  • Drop invalid UTF-8 candidates during class detection (#20389)
  • Prevent @tailwindcss/vite from forcing full-page reloads for scanned files that Vite does not handle as modules (e.g. .php files) (#20414)
  • Canonicalization: don't merge utilities that reference different theme variables set to CSS-wide keywords like unset (#20417)
  • Don't generate utilities when a modifier is used that would otherwise be silently ignored (e.g. rounded-sm/[5], shadow-sm/foo, stroke-2/50) (#20419)
  • Preserve and, or, and not inside selectors in supports-[…] variants (e.g. supports-[selector(a:not(.foo))]:flex) (#20420)
  • Don't warn about Angular's ::ng-deep and :host-context() when optimizing CSS (#20434)
  • Don't generate CSS for candidates containing an empty additional modifier (e.g. bg-red-500/50/ and group-hover/foo//bar:flex) (#20466)
  • Ensure min-*, max-*, and container query variants with decimal values are sorted numerically (e.g. min-[40.25rem] before min-[40.5rem]) (#20512)
  • Ensure CSS comments ending with \*/ are closed correctly instead of swallowing the CSS that follows (e.g. /* C:\temp\*/) (#20508)
  • Improve style invalidation performance of group-* and peer-* variants (#20513)
  • Ensure cached compilers release their loadModule and loadStylesheet callbacks after compilation (#20531)
  • Canonicalization: preserve & when moving a pseudo-element into * or ** (e.g. [&_::before]:flex → **:[&::before]:flex) (#20550)
  • Ensure the Set.prototype.intersection polyfill in canonicalizeCandidates(…) returns the intersection instead of the first set on Node.js < 22 (#20562)
  • Canonicalization: ensure inline theme(…) alphas with more than 2 decimals migrate to a percentage modifier with the same opacity (e.g. theme(colors.red.500/.12345) → text-red-500/[12.345%], not text-red-500/[12.345]) (#20563)
  • Canonicalization: preserve inline theme(…) alphas as an arbitrary percentage when a custom --opacity-* theme value would change the opacity (e.g. theme(colors.red.500/50%) → text-red-500/[50%] with --opacity-50: 10%) (#20563)
  • Ensure the @property fallback isn't applied in Safari versions that no longer support margin-trim: inline (#20569)
  • Treat viewport units like dvmin and svi and font-relative units like cap and rex as lengths in arbitrary values (e.g. text-[10dvmin] generates font-size instead of color) (#20516)
  • Write plugin logs to stderr in tailwindcss canonicalize so they don't end up in the results on stdout (#20561)
  • Extract class shorthands on later lines when Pug text, comments, or quoted attribute values contain unbalanced brackets, or a quote that doesn't start a string (e.g. input(pattern=/"/.source)) (#20547, #20572)

... (truncated)

Changelog

Sourced from tailwindcss's changelog.

[4.3.5] - 2026-11-06

Fixed

  • Canonicalization: improve performance in projects with many functional variant values (e.g. a matchVariant plugin with thousands of values) (#20663)
  • Don't crash or create a fallback with the wrong color for a color-mix(…) without a color interpolation method (e.g. color-mix(var(--color-red-500)) or color-mix(currentcolor 50%, transparent)) (#20658, #20666)
  • Ensure @tailwindcss/oxide-wasm32-wasi loads instead of hanging forever (e.g. with NAPI_RS_FORCE_WASI=error or in WebContainers) (#20667)
  • Remove as: '*.css' from the @tailwindcss/turbopack setup in its README, because it breaks CSS modules (#20660)
  • Ignore <!-- and --> between top-level rules in CSS instead of throwing or swallowing the next rule (e.g. a { color: re...

    Description has been truncated

    Note
    Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Oct 7, 2026
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Oct 7, 2026 •

Copy link
Copy Markdown

Deploying dikho with  Cloudflare Pages  Cloudflare Pages

Latest commit: a0753aa
Status:🚫  Build failed.

View logs

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Oct 7, 2026
@dependabot dependabot Bot changed the title chore(deps-dev): bump the dev-tooling group with 7 updates chore(deps-dev): bump the dev-tooling group across 1 directory with 7 updates Oct 14, 2026
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/dev-tooling-e7be97e4fe branch 2 times, most recently from eb4c25b to b94c81e Compare October 21, 2026 16:06
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/dev-tooling-e7be97e4fe branch 2 times, most recently from f955b84 to 6091c8d Compare November 4, 2026 16:06
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/dev-tooling-e7be97e4fe branch from 6091c8d to 62d7d4d Compare November 5, 2026 00:55
… updates

Bumps the dev-tooling group with 7 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [@cloudflare/vite-plugin](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/vite-plugin-cloudflare) | `1.62.3` | `1.67.0` |
| [@vitejs/plugin-react](https://github.com/vitejs/vite-plugin-react/tree/HEAD/packages/plugin-react) | `6.0.5` | `6.2.1` |
| [oxlint](https://github.com/oxc-project/oxc/tree/HEAD/npm/oxlint) | `1.78.0` | `1.92.0` |
| [supabase](https://github.com/supabase/cli/tree/HEAD/apps/cli) | `2.118.0` | `3.0.0` |
| [tailwindcss](https://github.com/tailwindlabs/tailwindcss/tree/HEAD/packages/tailwindcss) | `3.4.19` | `4.3.5` |
| [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) | `8.2.1` | `8.3.6` |
| [wrangler](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/wrangler) | `4.145.0` | `4.156.1` |



Updates `@cloudflare/vite-plugin` from 1.62.3 to 1.67.0
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Changelog](https://github.com/cloudflare/workers-sdk/blob/@cloudflare/vite-plugin@1.67.0/packages/vite-plugin-cloudflare/CHANGELOG.md)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/@cloudflare/vite-plugin@1.67.0/packages/vite-plugin-cloudflare)

Updates `@vitejs/plugin-react` from 6.0.5 to 6.2.1
- [Release notes](https://github.com/vitejs/vite-plugin-react/releases)
- [Changelog](https://github.com/vitejs/vite-plugin-react/blob/main/packages/plugin-react/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite-plugin-react/commits/plugin-react@6.2.1/packages/plugin-react)

Updates `oxlint` from 1.78.0 to 1.92.0
- [Release notes](https://github.com/oxc-project/oxc/releases)
- [Changelog](https://github.com/oxc-project/oxc/blob/main/npm/oxlint/CHANGELOG.md)
- [Commits](https://github.com/oxc-project/oxc/commits/oxlint_v1.92.0/npm/oxlint)

Updates `supabase` from 2.118.0 to 3.0.0
- [Release notes](https://github.com/supabase/cli/releases)
- [Changelog](https://github.com/supabase/cli/blob/develop/apps/cli/docs/release-process.md)
- [Commits](https://github.com/supabase/cli/commits/v3.0.0/apps/cli)

Updates `tailwindcss` from 3.4.19 to 4.3.5
- [Release notes](https://github.com/tailwindlabs/tailwindcss/releases)
- [Changelog](https://github.com/tailwindlabs/tailwindcss/blob/main/CHANGELOG.md)
- [Commits](https://github.com/tailwindlabs/tailwindcss/commits/v4.3.5/packages/tailwindcss)

Updates `vite` from 8.2.1 to 8.3.6
- [Release notes](https://github.com/vitejs/vite/releases)
- [Changelog](https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite/commits/v8.3.6/packages/vite)

Updates `wrangler` from 4.145.0 to 4.156.1
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.156.1/packages/wrangler)

---
updated-dependencies:
- dependency-name: "@cloudflare/vite-plugin"
  dependency-version: 1.62.5
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dev-tooling
- dependency-name: "@vitejs/plugin-react"
  dependency-version: 6.1.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dev-tooling
- dependency-name: oxlint
  dependency-version: 1.86.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dev-tooling
- dependency-name: supabase
  dependency-version: 2.119.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dev-tooling
- dependency-name: tailwindcss
  dependency-version: 4.3.3
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: dev-tooling
- dependency-name: vite
  dependency-version: 8.3.2
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dev-tooling
- dependency-name: wrangler
  dependency-version: 4.147.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dev-tooling
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/dev-tooling-e7be97e4fe branch from 62d7d4d to a0753aa Compare November 11, 2026 16:06
@Axoineo

Axoineo commented Nov 19, 2026

Copy link
Copy Markdown
Owner

The routine parts are in #61. Tailwind CSS 4 is left out on purpose: it changes how all styling is built and is what broke this build. It needs its own migration.

@Axoineo Axoineo closed this Nov 19, 2026
@dependabot @github

dependabot Bot commented on behalf of github Nov 19, 2026

Copy link
Copy Markdown
Contributor Author

This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests.

To ignore these dependencies, configure ignore rules in dependabot.yml

@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/dev-tooling-e7be97e4fe branch November 19, 2026 08:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant