fix(release): ensure leading v is stripped from provided semver version

[JamesHenry]

Current Behavior

v17.2.5 was accidentally published (with a leading v) and it turns out that the node semver package feels the leading v is valid and therefore we happily stamped the full v17.2.5 out into our package.json files.

Expected Behavior

Now even if such an accidental publish were to happen, the leading v would always be stripped before applying it.

Related Issue(s)

Fixes #

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment

Name	Status	Preview	Updated (UTC)
nx-dev	⬜️ Ignored (Inspect)	Visit Preview	Dec 17, 2023 0:09am

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 8baf44b. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 6 targets

• nx affected --target=e2e --base=71ce32a1217913123b83da5fe995e3fc77f05848 --head=8baf44bf4f007e4dc88e8aeefaa02e7bcd3dc6fb --parallel=1
• nx run-many -t check-imports check-commit check-lock-files check-codeowners documentation --parallel=1 --no-dte
• nx affected --targets=lint,test,build --base=71ce32a1217913123b83da5fe995e3fc77f05848 --head=8baf44bf4f007e4dc88e8aeefaa02e7bcd3dc6fb --parallel=3
• nx-cloud record -- nx format:check --base=71ce32a1217913123b83da5fe995e3fc77f05848 --head=8baf44bf4f007e4dc88e8aeefaa02e7bcd3dc6fb
• nx documentation --no-dte
• nx affected -t e2e-macos --parallel=1 --base=71ce32a1217913123b83da5fe995e3fc77f05848 --head=8baf44bf4f007e4dc88e8aeefaa02e7bcd3dc6fb

---

Sent with 💌 from NxCloud.

[github-actions]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.