[octavian-snyk]

Pull Request Submission Checklist

• Follows CONTRIBUTING guidelines
• Commit messages
  are release-note ready, emphasizing
  what was changed, not how.
• Includes detailed description of changes
• Contains risk assessment (Low | Medium | High)
• Highlights breaking API changes (if applicable)
• Links to automated tests covering new functionality
• Includes manual testing instructions (if necessary)
• Updates relevant GitBook documentation (PR link: ___)
• Includes product update to be announced in the next stable release notes

What does this PR do?

Adds deps to the commit types Danger accepts. This is temporary. The sync PR #7410 carries the commit deps: bump yao-pkg from release-candidate, and Danger fails it because deps is not an allowed type. The next PR in the stack reverts this change.

Where should the reviewer start?

The one-line regex change in dangerfile.js.

How should this be manually tested?

Rebase #7410 on this branch. The Danger status should pass.

What's the product update that needs to be communicated to CLI users?

None.

Risk assessment

Low. CI-only change.

🤖 Generated with Claude Code

---

Note

Low Risk
CI-only Danger rule change with no runtime or product impact.

Overview
Temporarily extends Danger’s commit-message validation to accept the deps type (e.g. deps: bump yao-pkg), so stacked/sync PRs aren’t blocked by CI while that convention exists on another branch.

The change is a single regex update in dangerfile.js adding deps to the allowed conventional-commit prefixes; a follow-up PR is expected to remove it again.

^{Reviewed by Cursor Bugbot for commit f3d11f3. Bugbot is set up for automated code reviews on this repo. Configure here.}

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[snyk-pr-review-bot]

PR Reviewer Guide 🔍

🧪 PR contains tests

🔒 No security concerns identified

⚡ No major issues detected

📚 Repository Context Analyzed This review considered 3 relevant code sections from 3 files (average relevance: 0.64) CONTRIBUTING.md (lines 311-480) CLAUDE.md (lines 152-274) dangerfile.js (lines 1-111)

🤖 Repository instructions applied (from AGENTS.md)