[dipto0321]

Summary

Release-prep PR for v1.2.0. The version is bumped in both the Go
release and the npm wrapper so the two ship together, and the
CHANGELOG gains a v1.2.0 section describing what landed.

The release ships one feature: Vite+ support (#124), which brings
the supported-manager count from 8 to 9.

Version bumps

File	Field	Before	After
nodeup-npm/package.json	version	1.1.0	1.2.0
nodeup-npm/package.json	binaryVersion	1.1.0	1.2.0

The two must match: the wrapper's postinstall downloads the archive
named nodeup_<binaryVersion>_<os>_<arch>.{tar.gz,zip} from the
v<binaryVersion> GitHub release. A mismatch would 404 at install
time.

CHANGELOG

New ## [1.2.0] - 2026-11-01 section covering:

• The VitePlus manager — detection, version parsing, installed-version
  listing, active-version query, the four mutations, and global npm
  prefix resolution
• The data-directory resolution chain (VP_HOME → <home>/.vite-plus →
  VP_DATA_DIR → XDG/platform default) and why all candidates are
  returned rather than just the first hit
• The system_first mode subtlety: Current() errors there, so cleanup
  fails closed instead of attributing a system install to the managed set
• The Windows vp.exe detection fix

Also refreshed the version-link footer at the bottom of the file.

Docs

File	Change
README.md	Project-status table: current release → v1.2.0, npm wrapper → nodeupx@1.2.0, phase 8 row now names all three releases
docs/managers.md	Detection-matrix header → "as of v1.2.0"; status note → nodeupx@1.2.0
CLAUDE.md	Phase-8 row → "v1.0.0 → v1.2.0 releases"
SPEC.md	Refresh date → 2026-11-01; new T22 row for the Vite+ work

Verification

• make ci green (tidy + fmt + vet + lint + race tests)
• npm pack --dry-run in nodeup-npm/ — exactly 5 files
  (LICENSE, README.md, package.json, scripts/check.js,
  scripts/install.js); no bin/, no node_modules/
• wrapper version === binaryVersion asserted
• GoReleaser snapshot release against v2.19.0 (the version
  release.yml's version: latest resolves to today) — all 5
  platform binaries, checksums.txt, the Homebrew formula, and the
  Scoop manifest build clean
• Archive naming verified to match the shape the npm wrapper
  expects: nodeup_<version>_<os>_<arch>.{tar.gz,zip}, matching the
  asset names on the existing v1.1.0 release
• Built binary smoke-tested (nodeup version reports the injected
  version/commit/date)

Notes for the reviewer

• The goreleaser check run reports three deprecation warnings
  (archives.format, archives.format_overrides.format, brews), all
  pre-existing and non-fatal — the snapshot release completes cleanly
  against v2.19.0. Cleaning them up is a separate change; doing it here
  would muddy a version-bump PR.
• goreleaser also logs ldflags is defined twice. This is GoReleaser's
  own default ldflags colliding with the explicit flags: in
  .goreleaser.yaml. Harmless today (the explicit flag wins, and the
  built binary reports the correct version/commit/date — verified above),
  but worth a follow-up to drop the redundant flags: block.

Test plan

• CI green on ubuntu / macos / windows
• Post-merge: tag v1.2.0, confirm the release workflow publishes
  all 5 binaries + checksums, and confirm npm view nodeupx version
  reports 1.2.0

🤖 Generated with puku-cli

[cocogitto-bot]

✔️ 1cef54e - Conventional commits check succeeded.