Skip to content

chore: bump Node to 26 and refresh mise tools - #7687

Open
jgoux wants to merge 1 commit into
developfrom
chore/node-26-mise-updates
Open

jgoux wants to merge 1 commit into
developfrom
chore/node-26-mise-updates

Conversation

@jgoux

@jgoux jgoux commented Nov 18, 2026

Copy link
Copy Markdown
Contributor

Summary

Mirrors supabase/supabase#53589 and refreshes the rest of the mise-managed toolchain:

  • Node 24 → 26 LTS (26.13.1), including the npm-only publish job in release-config.yml
  • pnpm 12.15.0 → 12.19.0
  • jactionlint 2.3.0 → 2.5.0
  • jdx/mise-action v5.2.2 → v5.2.7
  • mise.lock regenerated

Each version is the newest release past the repository's 7-day cooldown (Dependabot cooldown / pnpm minimumReleaseAge). mise 2026.11.6, Bun 1.4.4 and shellcheck 0.11.0 are already current under that rule.

This touches .github/actions/setup, which is release infrastructure, but only the mise-action pin changes; v2.x does not need a backport.

Move the toolchain to Node 26 LTS and pnpm 12.19.0, bump jactionlint to
2.5.0 and jdx/mise-action to v5.2.7, and regenerate mise.lock. Versions
respect the repository's 7-day release cooldown.
@jgoux
jgoux requested review from a team and supabase-oss as code owners November 18, 2026 10:22
@jgoux
jgoux requested a review from avallete November 18, 2026 10:22
@jgoux jgoux self-assigned this Nov 18, 2026
@github-actions

Copy link
Copy Markdown
Contributor

CLI benchmark (Lightweight Commands): no changes found

Commit 519e79c against develop at 769cf90 · 10 runs each · report only, never blocks merging

Command Workload Before After Change
supabase --version version 247 ms 262 ms no real change (+6%, within normal variation)
supabase --help help 205 ms 220 ms no real change (+7%, within normal variation)
supabase init init 220 ms 214 ms no real change
supabase migration new bench migration-new 225 ms 216 ms no real change
supabase config convert config-convert 176 ms 178 ms no real change
supabase config validate config-validate 173 ms 175 ms no real change
supabase gen types --lang typescript --project-id replayfixtureprojref gen-types 221 ms 223 ms no real change
supabase projects list projects-list 244 ms 240 ms no real change
supabase functions list --project-ref replayfixtureprojref functions-list 251 ms 241 ms no real change

API calls: unchanged for all 9 commands.

Binary size: 135.2 MB, unchanged.

Details: timing ranges, API calls per command, slowest phases

Timing ranges

Command Workload Before range After range Change Verdict
supabase --version version 199-323 ms 220-306 ms +15 ms (+6%) within noise
supabase --help help 188-253 ms 186-276 ms +15 ms (+7%) within noise
supabase init init 198-279 ms 198-262 ms -5 ms (-2%) within noise
supabase migration new bench migration-new 169-299 ms 175-246 ms -10 ms (-4%) within noise
supabase config convert config-convert 170-208 ms 169-190 ms +3 ms (+2%) within noise
supabase config validate config-validate 170-203 ms 172-232 ms +2 ms (+1%) within noise
supabase gen types --lang typescript --project-id replayfixtureprojref gen-types 189-298 ms 187-249 ms +3 ms (+1%) within noise
supabase projects list projects-list 211-299 ms 203-337 ms -3 ms (-1%) within noise
supabase functions list --project-ref replayfixtureprojref functions-list 217-260 ms 202-302 ms -10 ms (-4%) within noise

API calls per command

Command Workload Before After Endpoint changes
supabase --version version 0 0
supabase --help help 0 0
supabase init init 0 0
supabase migration new bench migration-new 0 0
supabase config convert config-convert 0 0
supabase config validate config-validate 0 0
supabase gen types --lang typescript --project-id replayfixtureprojref gen-types 2 2
supabase projects list projects-list 1 1
supabase functions list --project-ref replayfixtureprojref functions-list 2 2

Slowest phases

No command moved beyond noise, so there are no phase deltas.

Workflow run

Comment /bench to run the lightweight benchmark (this comment) again on the latest commit, or /bench full to also run the integration-heavy benchmark, which posts in its own comment.

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 AI Review

CLI reference prose guidance: not applicable (no reference sources changed).

Both independent reviews completed with no findings. My review of the diff and surrounding code found no concrete issues: toolchain pins and lockfile references are consistent, and the supplied next-branch work has no fundamental conflict. CLI reference prose review was not applicable. Validation was limited to static inspection and structural consistency checks; tool downloads and CI were not run.

Findings

No issues found.

Stats

Claude findings: 0 · Codex findings: 0 · Confirmed: 0 · Refuted: 0 · Uncertain: 0


Models: claude-opus-5-5 + gpt-6.1-sol · Trigger: auto · Workflow run

This review runs once per PR. A maintainer can request another with a /ai-review comment.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants