Trim v prefix from shipIt's version to avoid double prefixing tags

[ghengeveld]

Auto shipIt's newVersion field is prefixed with v (e.g. v11.2.0), whilst the version field in package.json is not. This was causing the tags on the GitHub Action repo to be double-prefixed, e.g. vv11.2.0. Trimming the prefix from newVersion avoids that.

📦 Published PR as canary version: 11.3.1--canary.960.8480061188.0

✨ Test out this PR locally via:

npm install chromatic@11.3.1--canary.960.8480061188.0
# or 
yarn add chromatic@11.3.1--canary.960.8480061188.0

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
Report missing for cf7b2371	✅ ∅

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (cf7b237)	Report Missing	Report Missing	Report Missing
Head commit (8b1e88d)	8445	6640	78.63%

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#960)	0	0	∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

_{You may notice some variations in coverage metrics with the latest Coverage engine update. For more details, visit the documentation}

Footnotes

1. Codacy didn't receive coverage data for the commit, or there was an error processing the received data. Check your integration for errors and validate that your coverage setup is correct. ↩

[tmeasday]

LGTM

[ghengeveld]

🚀 PR was released in v11.3.0 🚀