ci: fix workflow concurrency and composite action drift

[pratyush618]

Three CI-hygiene fixes surfaced while triaging #465, where CodeQL's Analyze (javascript-typescript) sat queued for minutes and the security gate reported 1 configuration not found.

Concurrency groups. semantic-pr.yml had no group and fires on opened|edited|reopened|synchronize, so dependabot's open+rebase burst stacked three identical runs that starved the runner queue. Added groups to semantic-pr.yml, labeler.yml, codeql.yml and actionlint.yml. Two details worth noting:

• pull_request_target resolves github.ref to the base branch, so the two workflows using that trigger key on github.event.pull_request.number — keying on the ref would make every open PR share one group and cancel the others.
• CodeQL cancels PR scans only. Master and scheduled scans run to completion so their alerts still reach the security dashboard.

Composite action drift. The github-actions dependabot entry used directory: /, which covers .github/workflows/** and nothing else, so the composites under .github/actions/** stayed on actions/setup-node@v6 / actions/setup-python@v6 while the workflows moved to v7. Those composites are what the Rust/Python/Node suites actually call. Bumped all three and switched dependabot to directories: [/, /.github/actions/*] so they stay in sync.

v7 is a major on both actions, but the only removed input is setup-python's pip-install, which this repo does not use.

Summary by CodeRabbit

• Chores
  • Updated automated build and validation workflows to use the latest Node.js and Python setup actions.
  • Improved automation monitoring so workflow updates include composite actions.
  • Added concurrency controls to prevent outdated workflow runs from continuing unnecessarily.
  • Preserved completion of important security scans while allowing superseded pull request checks to be cancelled.
  • Improved consistency and efficiency across labeling, validation, build, and security workflows.

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 49 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: bb330b8c-a22c-4a5b-9bf2-cf379aa46cab

📥 Commits

Reviewing files that changed from the base of the PR and between bf3193b and b7e179d.

📒 Files selected for processing (8)

• .github/actions/dashboard-build/action.yml
• .github/actions/setup-node/action.yml
• .github/actions/setup-python/action.yml
• .github/dependabot.yml
• .github/workflows/actionlint.yml
• .github/workflows/codeql.yml
• .github/workflows/labeler.yml
• .github/workflows/semantic-pr.yml

📝 Walkthrough

Walkthrough

GitHub Actions setup references were upgraded to v7, Dependabot coverage was expanded to composite actions, and concurrency policies were added to four workflows with workflow-, ref-, or pull-request-based grouping.

Changes

GitHub Actions maintenance

Layer / File(s)	Summary
Action runtime versions and Dependabot coverage .github/actions/*/action.yml, .github/dependabot.yml	Node.js and Python setup actions now use v7, while Dependabot monitors both root workflows and composite actions.
Workflow concurrency policies .github/workflows/actionlint.yml, .github/workflows/codeql.yml, .github/workflows/labeler.yml, .github/workflows/semantic-pr.yml	Workflows now group overlapping runs and apply cancellation rules based on refs, workflow names, and pull request numbers.

Estimated code review effort: 2 (Simple) | ~10 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main CI concurrency updates and composite action version bumps in this PR.
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

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/ci-concurrency-and-action-bumps

---

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