[dependabot]

Bumps supabase/setup-cli from 3.0.1 to 3.2.0.

Release notes

Sourced from supabase/setup-cli's releases.

v3.2.0

Summary

• version accepts npm semver ranges, like ^2, ^2.95, ~2.98.0, 2.x, >=2.98 <2.99, or ^1 || ^2 (#459).
  • A range installs the version npm picks: latest if it matches, otherwise the highest non-deprecated match.
  • The action logs which exact version a range resolved to, and installs that exact version.
• The README has an upgrade notice for v1 and v2 users: those majors are legacy, and @v3 can still install older CLIs with an exact version or a range like ^2 (#459).
• The action provisions Node.js with actions/setup-node v7 when the runner has none (#450).
• Development moved to stable TypeScript 7, and the Licensed check runs on ubuntu-24.04 (#460).

Validation

• CI and E2E passed on main before tagging.

v3 is the moving major-version alias for this release.

v3.1.0

Summary

• version accepts the next and v<N>.stable dist-tags, so a workflow can stay on an older major's maintenance line, for example version: v2.stable (#456).
• When npm can't install a working CLI yet, for example while a new release is still propagating, the action installs the same version from its GitHub release instead.
  • It verifies the download against the release's checksums.
  • It needs a fixed version, either requested or resolved by npm.
  • It is skipped when the lockfile integrity check fails.
  • The new install-source output reports npm or github-release. (#457)
• The README documents the v3 tag publish flow (#455).

Validation

• CI and E2E passed on main before tagging.

v3 is the moving major-version alias for this release.

Commits

• 689adcf chore: move to stable TypeScript 7 (#460)
• 30e7433 feat: resolve semver ranges in the version input (#459)
• 30c0cfb chore(deps): bump actions/setup-node from 6.4.0 to 7.0.0 (#450)
• d239d10 feat: fall back to the GitHub release when npm cannot install the CLI (#457)
• bea6372 feat: support next and v<N>.stable dist-tags (#456)
• adc7f6c docs: document the v3 tag publish flow (#455)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)