fix(ci): add workflow_dispatch trigger to release.yml

[jbdevprimary]

Summary

• Add workflow_dispatch trigger so the Release workflow can be manually run
• Needed because auto-merged release-please PRs don't trigger new workflow runs (GITHUB_TOKEN limitation)

Context

When release-please auto-merges its PR via GITHUB_TOKEN, the push to main doesn't create a new workflow run. This means release-please never gets a chance to detect the merged PR and create the GitHub Release + tag.

Workaround: After a release-please PR auto-merges, manually trigger the Release workflow.

Long-term fix: Use a PAT (Personal Access Token) as the token input for release-please-action. This allows the merged PR push to trigger workflows normally.

Test plan

• After merge, manually trigger Release workflow to create v1.0.0 release

🤖 Generated with Claude Code

[gemini-code-assist]

Note

Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported.

[coderabbitai]

Warning

Rate limit exceeded

@jbdevprimary has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 11 minutes and 25 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 00b4b0f and 0f0a97b.

📒 Files selected for processing (1)

• .github/workflows/release.yml

---

Note

🎁 Summarized by CodeRabbit Free

The PR author is not assigned a seat. To perform a comprehensive line-by-line review, please assign a seat to the pull request author through the subscription management page by visiting https://app.coderabbit.ai/login.

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

[amazon-q-developer]

Review Summary

🛑 Critical Logic Error - Workflow Won't Function as Intended

The workflow_dispatch trigger has been added correctly, but the workflow will not function when manually triggered. The release-please job has a condition on line 18:

if: github.event_name == 'push'

When the workflow is manually triggered, github.event_name will be workflow_dispatch, not push, causing the job to be skipped. This defeats the purpose stated in the PR description.

Required Fix:

Change line 18 to:

if: github.event_name == 'push' || github.event_name == 'workflow_dispatch'

This will allow the release-please job to run both on push events and when manually triggered, achieving the intended workaround for the GITHUB_TOKEN limitation.

---

You can now have the agent implement changes and create commits directly on your pull request's source branch. Simply comment with /q followed by your request in natural language to ask the agent to make changes.

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	85.36% (🎯 80%)	4595 / 5383
🔵	Statements	84.51% (🎯 80%)	4966 / 5876
🔵	Functions	82.88% (🎯 80%)	1492 / 1800
🔵	Branches	74.77% (🎯 73%)	2825 / 3778

File Coverage

No changed files found.

Generated in workflow #570 for commit 0f0a97b by the Vitest Coverage Report Action