feat: auto-trigger prod deployment on semver tags

[konradmichalik]

Summary

• Change prod deployment from manual to automatic trigger on semver tags (v1.2.3 or 1.2.3)

Changes

• deploy/deploy-prod.yaml - Switch when: manual to when: always for semver tag rule

[coderabbitai]

Warning

Rate limit exceeded

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

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 12 minutes and 29 seconds.

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

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: d035cbee-9d65-4b4e-987b-59ae6936f203

📥 Commits

Reviewing files that changed from the base of the PR and between f4b4543 and 9251ab4.

📒 Files selected for processing (1)

• deploy/deploy-prod.yaml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feature/auto-deploy-on-tag

---

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