chore(qa): 🤖 Allow skip pre-release, or release-cycle mode (initial)

[punkbit]

Why?

Allow a maintainer to skip pre-release when preparing to publish a new package version. A pre-release is part of the release cycle mode (e.g. test -> release-candidate (RC) -> stable -> latest), which helps get feedback as early as possible. Using skip pre-release bypasses quality safeguards and should only be used when the risk of not releasing "stable/latest" immediately exceeds the risk of potential regressions.

How?

• Introduce a "skip_prerelease" checkbox in "create release"
• Update generate and verify commit message scripts to support extended commit message, e.g. [skip-prerelease]
• Extend documentation with new use cases, instruction and related warnings

Contribution checklist?

• You've done enough research before writing
• You have reviewed the PR
• The commit messages are detailed
• The build command runs locally
• Assets or static content are linked and stored in the project
• For documentation, guides or references, you've tested the commands

Security checklist?

• All user inputs are validated and sanitized
• No usage of dangerouslySetInnerHTML
• Sensitive data has been identified and is being protected properly
• Build output contains no secrets or API keys

Preview?

[changeset-bot]

⚠️ No Changeset found

Latest commit: c28946e

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 1m 51s —— View job

---

PR Review

• Gather context
• Read changed files
• Analyze for issues
• Post review

---

All items from the previous review have been addressed in this update. Here's the full picture:

✅ Previous Must-Fix — Resolved

• docs/package-release.md:288 — [!WARN] → [!WARNING] is now correct. All admonition tags in the file are valid GitHub-flavored ones.

✅ Previous Suggestions — All Addressed

• release-publisher.yml:38 — Comment updated to reflect the new three-field output format (VERSION RELEASE_TYPE [skip_prerelease]).
• generate-release-commit-message — Now emits a stderr warning when skip_prerelease=true is used with test/rc release types, and still outputs a clean commit message (no [skip-prerelease] marker appended). Correct.
• create-release.yml:242 — The bash [[ "${{ inputs.skip_prerelease }}" != "true" ]] in a run: step vs. inputs.skip_prerelease != true in a YAML if: expression are both idiomatic for their respective contexts. No action needed.

No new issues found. The regex in verify-release-commit correctly makes [skip-prerelease] optional and orders it before the PR number suffix. The double-negative safeguard check in release-publisher.yml:68 (!= "skip_prerelease") is functional and mirrors the audit-trail string set by verify-release-commit.

✅ Looks great — solid, well-scoped implementation with good audit trail and appropriate safeguards. Nice work! 🙌

[workflow-authentication-public]

📚 Storybook Preview Deployed

✅ Preview URL: https://click-4jgnl9rku-clickhouse.vercel.app

Built from commit: a97c2a0dfb5049ec4aef899a68a0685cf38e5faa