Release 1.32.10-beta.0

[this-is-shivamsingh]

Version bump to 1.32.10-beta.0 (next prerelease off 1.32.9).

• Bumped via lerna version 1.32.10-beta.0 --exact --no-git-tag-version --no-push (the bump-version script's underlying command), and publishConfig.tag set to beta across all packages.
• 19 files changed: lerna.json + all 18 packages/*/package.json.
• On publishing a GitHub Release, this will go to npm under dist-tag beta.

Next steps: review & merge, then cut the GitHub Release.

🤖 Generated with Claude Code

[this-is-shivamsingh]

Claude Code PR Review

PR: #2424 • Head: 9e870ec • Reviewers: stack-code-reviewer

Summary

Release version-bump PR (Lerna monorepo): every package 1.32.9 → 1.32.10-beta.0, with publishConfig.tag flipped latest → beta and all internal @percy/* pins bumped in lockstep. 19 files (lerna.json + all 18 packages/*/package.json), no source changes.

Review Table

Priority	Category	Check	Status	Notes
High	Security	No hardcoded secrets or credentials	Pass	Version strings only.
High	Security	Authentication/authorization checks present	N/A	No auth surface.
High	Security	Input validation and sanitization	N/A	No runtime code changed.
High	Security	No IDOR — resource ownership validated	N/A	No runtime code changed.
High	Security	No SQL injection (parameterized queries)	N/A	No SQL.
High	Correctness	Logic is correct, handles edge cases	Pass	1.32.10-beta.0 is valid semver and correctly the next beta off 1.32.9; no 1.32.10* tag exists yet.
High	Correctness	Error handling is explicit, no swallowed exceptions	N/A	No logic.
High	Correctness	No race conditions or concurrency issues	N/A	No logic.
Medium	Testing	New code has corresponding tests	N/A	Version bump — no code to test.
Medium	Testing	Error paths and edge cases tested	N/A	—
Medium	Testing	Existing tests still pass (no regressions)	Pass	No source changes; nothing to regress.
Medium	Performance	No N+1 queries or unbounded data fetching	N/A	—
Medium	Performance	Long-running tasks use background jobs	N/A	—
Medium	Quality	Follows existing codebase patterns	Pass	Byte-for-byte matches prior Lerna release commits (e.g. #2419).
Medium	Quality	Changes are focused (single concern)	Pass	Only the 19 release files; no stray artifacts committed.
Low	Quality	Meaningful names, no dead code	N/A	—
Low	Quality	Comments explain why, not what	N/A	—
Low	Quality	No unnecessary dependencies added	Pass	External deps (ajv, pako, yaml, ws, …) untouched; only internal @percy/* pins bumped.

Findings

No findings. Reviewer (stack-code-reviewer) independently verified against the branch content (HEAD 9e870ec6) vs master:

• Version sequencing — git tag confirms latest release is v1.32.9; neither v1.32.10 nor v1.32.10-beta.0 exists. 1.32.10-beta.0 is the correct, non-colliding next beta, matching the repo convention (1.32.9 was preceded by 1.32.9-beta.0/1). The base already carries feat(core): upload the snapshot log to the logs endpoint, not as a resource (PPLT-6034) #2417 (PPLT-6034) landed after the 1.32.9 tag — the change driving this beta cycle.
• Internal pin consistency — git grep "1\.32\.9" across *.json returns zero matches; no package left referencing an old @percy/* pin.
• publishConfig.tag — all 18 published packages flipped to beta; no "private": true package that should be skipped; touched set exactly matches the 18 dirs under packages/.
• lerna.json / package.json parity — all version fields identically 1.32.10-beta.0; valid semver, > 1.32.9.

Non-blocking note (out of scope for this diff): confirm the CI publish step honors publishConfig.tag: beta (i.e. npm publish isn't overridden with --tag latest) when cutting the GitHub Release.

---

Verdict: PASS — clean, uniform, Lerna-generated version bump with no anomalies.