Possible npm/GitHub ‘latest’ drift after develop began publishing to npm latest (prerelease vs stable)

[masda70]

Describe the bug
supabase/setup-cli@v1 with version: latest installs CLI v2.67.1, but npm’s latest dist-tag points to v2.72.4. This makes “latest” resolve to an older version in CI. It might be expected if the action intentionally follows GitHub’s latest stable (non‑prerelease) release while npm’s latest dist‑tag can point to a prerelease, but that behavior isn’t obvious from the action’s usage. This mismatch likely started when develop began publishing to npm latest while GitHub releases remained marked as prerelease.

To Reproduce

1. Create a GitHub Actions workflow that runs supabase/setup-cli@v1 with version: latest.
2. Run supabase --version.
3. Observe the CLI version is 2.67.1.
4. Compare with npm latest dist-tag, which is 2.72.4.

Expected behavior
Either version: latest should align with npm’s latest dist-tag, or the action/docs should clarify that it follows GitHub “latest stable release” (non‑prerelease).

Additional context

• Likely change that introduced drift: commit 08d3e3f044 (“feat: deprecate beta channel on npm”, 2025‑11‑27). It updates package.json so develop publishes to channel latest (was beta) and removes the publish job in .github/workflows/release.yml that called tag-npm.yml to move npm latest on stable releases.
• release-beta.yml still publishes npm with npm publish --tag ${{ new-release-channel }} and marks the GitHub release as prerelease. That means npm latest can now point to prereleases while GitHub “latest release” stays on the last stable.
• GitHub releases mark 2.72.4 as prerelease; npm latest points to 2.72.4.
• Observed on January 12, 2026 in CI (ubuntu-latest).

Workflow snippet:

- uses: supabase/setup-cli@v1
  with:
    version: latest
- run: supabase --version