docs: 📝 add note for version format handling

[punkbit]

Why?

Add note for version format handling.

How?

• Update package release documentation

Tickets?

N/A

Preview?

N/A

[changeset-bot]

⚠️ No Changeset found

Latest commit: 71bb1bc

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

Claude finished @punkbit's task in 24s —— View job

---

Review

• Gather context
• Read changed file
• Provide review

---

✅ Looks great! No issues found — nice work!

The added note (lines 27–32) is clear, accurate, and well-placed right after the overview paragraph. It correctly documents the v prefix behavior across commit messages, version extraction, CHANGELOG headers, git tags, branch names, and GitHub releases. The [!NOTE] callout format is consistent with the rest of the document.

[workflow-authentication-public]

📚 Storybook Preview Deployed

✅ Preview URL: https://click-28ruji0qw-clickhouse.vercel.app

Built from commit: a4f144f6e786710e04ad8b3aefafc7c9dd505a8a