Add suffix input to publish-new-version workflow

[gpunto]

Goal

Closes AND-1369

release.yml already accepts a suffix input, but this repo's own publish-new-version.yml never exposed or forwarded it, so we couldn't cut a suffixed release (e.g. v0.14.0-rc01) of the conventions from the Actions UI. Chat already does this.

Implementation

• Add an optional suffix string input to the workflow_dispatch trigger
• Forward it to release.yml

Testing

Dispatching without a suffix behaves as before. With a suffix, the version becomes X.Y.Z-suffix and the GitHub release is marked as a prerelease and not latest.

Checklist

• Issue linked (if any)
• Tests/docs updated
• I have signed the Stream CLA (required for external contributors)

Summary by CodeRabbit

• New Features
  • Added an optional version suffix when manually starting a new release.
  • The provided suffix is carried through the release process.

[github-actions]

PR checklist ✅

All required conditions are satisfied:

• Title length is OK (or ignored by label).
• At least one pr: label exists.
• Sections ### Goal, ### Implementation, and ### Testing are filled, or the PR is bot-authored.
• An issue is linked (Linear ticket or GitHub issue), or the PR is bot-authored.

🎉 Great job! This PR is ready for review.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: d08223c6-64a6-4526-852c-a1b4032a149b

📥 Commits

Reviewing files that changed from the base of the PR and between ec1d49b and 366c13b.

📒 Files selected for processing (1)

• .github/workflows/publish-new-version.yml

---

Walkthrough

The publish workflow now accepts an optional version suffix. It forwards the suffix to the reusable release workflow and documents automatic dash handling.

Changes

Release suffix

Layer / File(s)	Summary
Accept and forward version suffix .github/workflows/publish-new-version.yml	The workflow accepts an optional suffix input with an empty default and passes it to the reusable release workflow.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Poem

I’m a rabbit with a version tag,
Adding suffixes to the release flag.
A dash appears when it should be,
The workflow hops along happily.
Ship the build—one, two, three!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main workflow change.
Description check	✅ Passed	The description includes the goal, implementation, testing notes, linked issue, and checklist, with only non-critical checklist items incomplete.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches 💡 1

🛠️ Fix failing CI checks 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch ci/add-suffix-input-publish-new-version

---

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.}