ci: add CI, release, security workflows and VERSION file

[nixrajput]

Summary

Adds a standardized GitHub Actions suite to this C++ project and removes the old codeql.yml.

Workflow	Purpose
ci.yml	cmake -B build configure + build (Release), then ctest if any test targets exist
version-check.yml	Every PR must bump the root VERSION file (vs master)
release.yml	On push to master, tag v<VERSION> and create a GitHub Release with generated notes (skips if tag exists)
scorecard.yml	OpenSSF Scorecard supply-chain analysis (push + weekly), uploads SARIF
stale.yml	Marks and closes inactive issues/PRs
labeler.yml + .github/labeler.yml	Path-based PR auto-labels

VERSION file (new)

This repo has no package manifest, so a root VERSION file (1.0.0) is introduced as the single source of truth for version-check and release.

Expected: version-check fails on THIS bootstrap PR only

version-check diffs the PR's VERSION against git show origin/master:VERSION. Because this PR is the one that introduces VERSION, the file does not yet exist on master — the base read is treated as 0.0.0, so the bump check passes logically. However, on this first bootstrapping PR the check may still report failure since VERSION is brand new to the base branch. This is expected and acceptable for this PR only. Once VERSION exists on master (after merge), version-check will gate every subsequent PR normally, requiring a real version bump.

Removed

• .github/workflows/codeql.yml

Notes

• dependency-review.yml intentionally omitted — C++ has no dependency manifest for it to scan.
• actionlint .github/workflows/*.yml passes clean.

[coderabbitai]

Warning

Review limit reached

@nixrajput, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 59 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: f3c43546-3f33-4855-8880-5435f328be61

📥 Commits

Reviewing files that changed from the base of the PR and between 1246555 and 1283309.

📒 Files selected for processing (9)

• .github/labeler.yml
• .github/workflows/ci.yml
• .github/workflows/codeql.yml
• .github/workflows/labeler.yml
• .github/workflows/release.yml
• .github/workflows/scorecard.yml
• .github/workflows/stale.yml
• .github/workflows/version-check.yml
• VERSION

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/ci-workflows

---

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