chore: change deps review to fail on moderate

[mrTuomoK]

The previous fail-on-severity: low was a bit too aggressive -> moderate

Summary by CodeRabbit

• Chores
  • Adjusted automated dependency checks so the build only fails for moderate or higher-severity issues, reducing unnecessary failures from lower-severity alerts.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 55 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: 690c838d-f45c-4f38-9e0c-3d7e65057de9

📥 Commits

Reviewing files that changed from the base of the PR and between 57e8a95 and 836c86b.

📒 Files selected for processing (2)

• .github/workflows/ci-node.yml
• .github/workflows/ci-pnpm-node.yml

📝 Walkthrough

Walkthrough

The dependency-review job in the CI workflow's fail-on-severity setting was changed from "low" to "moderate," altering the threshold at which the workflow fails due to dependency vulnerabilities.

Changes

CI Dependency Review Threshold

Layer / File(s)	Summary
Severity threshold update .github/workflows/ci-pnpm-node.yml	Changed fail-on-severity input for actions/dependency-review-action from low to moderate.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• City-of-Helsinki/.github#43: Modifies the same fail-on-severity setting for the dependency-review-action in the same workflow file.

Suggested reviewers: mikkojamG, nicobav

🚥 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 workflow change to raise dependency review failure threshold to moderate.
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 deps-review-fail-on-moderate

---

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

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/workflows/ci-pnpm-node.yml:
- Line 268: The dependency-review threshold in the pnpm/node workflow is now
looser than the matching reusable CI workflows, creating inconsistent security
gating. Update the `fail-on-severity` setting in the `dependency-review` step of
`ci-pnpm-node.yml` to match the same bar used by `ci-node.yml` and
`ci-django-api.yml`, or make the divergence explicit and consistent across the
related workflow definitions.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 205d41a0-c8b4-495c-9c1e-af8f8a44aa40

📥 Commits

Reviewing files that changed from the base of the PR and between 77d8d34 and 57e8a95.

📒 Files selected for processing (1)

• .github/workflows/ci-pnpm-node.yml