Jason Jean
714c2313ed
## Current Behavior The repo's `mise.toml` defaults the Node.js toolchain to `24.11.0`. Contributors — and the mise-provisioned CI jobs (`ci.yml`, CodeQL) — therefore run on Node 24, which ships npm 11.6.1. That npm is too old to honor the `min-release-age` supply-chain cooldown (added in npm 11.10.0). ## Expected Behavior `mise.toml` defaults the Node.js toolchain to `26.3.0` (latest Node, ships npm 11.16.0). Local development and the mise-provisioned CI jobs move to Node 26. Scope / notes: - The default remains overridable via the `NODE_VERSION` env var — the template is otherwise unchanged. - `publish.yml` (pinned `NODE_VERSION: 22.16.0` plus hardcoded musl native builds) and `e2e-matrix.yml` (matrix `node_version`) set `NODE_VERSION` explicitly, so they are **unaffected** and stay on Node 22. - Utility workflows using `actions/setup-node` (`pr-title-validation`, `generate-embeddings`, `banner-monitor`, `issue-notifier`) remain on Node 24 and are out of scope for this change. - CI on this PR validates that the core build/test/lint suite passes on Node 26. ## Related Issue(s) N/A — internal toolchain bump.
18 lines
515 B
TOML
18 lines
515 B
TOML
[tools]
|
|
bun = "1.3"
|
|
java = "24"
|
|
node = "{{ env['NODE_VERSION'] | default(value='26.3.0') }}"
|
|
maven = "3.9.11"
|
|
rust = "1.95.0"
|
|
vale = "3.13.1"
|
|
|
|
# Ensure that the packageManager field gets used to resolve the correct version of pnpm
|
|
# https://github.com/jdx/mise/discussions/3549#discussioncomment-11918572
|
|
"npm:corepack" = "latest"
|
|
|
|
# dotnet via mise only works on Linux/macOS.
|
|
# On Windows, the vfox plugin is buggy: https://github.com/jdx/mise/discussions/4738
|
|
[tools.dotnet]
|
|
version = "9"
|
|
os = ["linux", "macos"]
|