ci: add version-check, security and maintenance workflows#13
Conversation
Add a root VERSION file (1.0.0) and a version-check workflow that enforces a VERSION bump on every PR to main. The GoReleaser release flow is unchanged and still cuts binary releases on manually pushed v* tags. Also add security and maintenance workflows: dependency-review (go.mod present), OpenSSF scorecard, stale issue/PR triage, and path-based PR labeler (.github/labeler.yml). Existing ci.yml and release.yml are left untouched.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Review limit reached
Next review available in: 59 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (7)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
What
Adds a root
VERSIONfile and standardized security/maintenance workflows. The existingci.yml(Go lint+test matrix) andrelease.yml(GoReleaser) are left unchanged.VERSION gate
VERSIONfile, seeded to1.0.0(the current released tag).version-check.ymlruns on every PR tomainand fails unlessVERSIONis bumped to a higher semver than the base branch. The template treats a missing baseVERSIONas0.0.0, so this introductory PR passes.Releases unchanged
Binary releases are still cut manually: push a
v*tag and GoReleaser (release.yml) takes over. There is no auto-tagging. TheVERSIONfile only gates PRs; it does not trigger releases.Security + maintenance workflows added
dependency-review.yml— flags vulnerable / disallowed-license deps on PRs (repo hasgo.mod).scorecard.yml— OpenSSF Scorecard, uploads SARIF to the Security tab.stale.yml— triages inactive issues/PRs.labeler.yml+.github/labeler.yml— path-based PR auto-labels.actionlintpasses clean on all new workflows.