feat(releases): add a manual trigger for the package release workflow

[myftija]

The manual trigger is currently enabled only for the prerelease job. This PR adds it for the normal release flow too, as it is useful to retrigger failed release workflows.

[changeset-bot]

⚠️ No Changeset found

Latest commit: c5bcc66

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

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The release workflow was refactored to support distinct release and prerelease flows. The workflow inputs changed from a single ref input to a multi-variant approach with a new type selector (release/prerelease), prerelease_ref, and prerelease_tag inputs. The workflow dispatch logic was updated to trigger conditionally based on release type, and all workflow steps that previously referenced inputs.ref and inputs.tag now reference the appropriate prerelease_ref and prerelease_tag inputs. Checkout steps were made explicit with branch references, and prerelease job gating was extended to require workflow dispatch with type prerelease.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

• Verify that all references to the old inputs.ref and inputs.tag have been replaced with inputs.prerelease_ref and inputs.prerelease_tag throughout the workflow
• Review the conditional logic for workflow_dispatch filtering to ensure the release and prerelease paths are correctly gated and mutually exclusive
• Confirm that checkout steps specify the correct ref values, particularly for main branch and prerelease_ref scenarios
• Validate that the validation step's main-branch ancestry check now correctly references prerelease_ref
• Ensure changeset versioning and publishing commands use the appropriate tag input for their respective flows

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch changesets-release-manual-trigger

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 07a1d04 and c5bcc66.

📒 Files selected for processing (1)

• .github/workflows/release.yml (6 hunks)

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}