You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Step 1 of the v2.8.0 release, per the release skill.
The bump goes on v2/mainbefore the milestone merge (#2010), so the release lands on main with the version already correct and v2/main is never left behind main.
Scope of this PR — all three parts of release prep, in one change:
Any fixes that audit forces, each as its own commit.
npm version minor --no-git-tag-version → 2.7.0 → 2.8.0. --no-git-tag-version is load-bearing: the release tag must point at the merge commit on main, not at a v2/main commit.
Step 1 of the v2.8.0 release, per the
releaseskill.The bump goes on
v2/mainbefore the milestone merge (#2010), so the release lands onmainwith the version already correct andv2/mainis never left behindmain.Scope of this PR — all three parts of release prep, in one change:
npm audit --audit-level=highacross the root and all four client installs, as a report. Anything it names is fixed deliberately — a direct bump or anoverridesentry — never withnpm audit fix(High-severity nanoid advisory in the production tree (via vite → postcss), on both branches #2058).npm version minor --no-git-tag-version→2.7.0→2.8.0.--no-git-tag-versionis load-bearing: the release tag must point at the merge commit onmain, not at av2/maincommit.Verified by
npm run local:gate.