Skip to content

ci: CI that tests, Dependabot, unused packages, branch-name hook (MKT-19723) - #147

Draft
pritesh-jain-cstk wants to merge 4 commits into
claude/test/MKT-19722-tests-from-specfrom
claude/ci/MKT-19723-ci-dependabot
Draft

pritesh-jain-cstk wants to merge 4 commits into
claude/test/MKT-19722-tests-from-specfrom
claude/ci/MKT-19723-ci-dependabot

Conversation

@pritesh-jain-cstk

@pritesh-jain-cstk pritesh-jain-cstk commented Oct 30, 2026 •

Copy link
Copy Markdown

Branch graph

graph LR
  tests["[Tests] MKT-19722 #146"]
  routine["[Routine] MKT-19723 #147"]
  docs["[Docs] MKT-20340 #148"]
  main --> tests
  tests --> routine
  main --> docs
  style routine fill:#ffd54f,stroke:#e65100,stroke-width:3px
Loading

Depends on #146. Split from #145. Merge order: tests, routine; docs is independent but stays draft until tests merge.

What

[Routine] Story MKT-19723, under Epic MKT-19715. Stacked on tests because the workflow runs the test suite. The branch-name hook commit comes first so that the later commits on claude/<type>/<KEY>-<slug> branches pass it. Dependabot is also tracked under Security story MKT-19724.

Sub-task Commit
MKT-20339 branch-name hook chore: accept MKT keys and claude branch names in the branch-name hook
MKT-20336 CI workflow ci: lint, typecheck, build and coverage workflow
MKT-20337 Dependabot ci: add Dependabot
MKT-20338 package cleanup chore: drop unused jotai and nth-check, add lint and typecheck scripts

Results

Run by CI on this PR (see checks): lint, typecheck, build, coverage. The validate-branch-name pattern only allowed feature|bugfix|hotfix/ESI-..., a retired project; it now also accepts MKT keys and the claude/<type>/<KEY>-<slug> form.

🤖 Generated with Claude Code

PriteshJain and others added 4 commits October 30, 2026 16:05
…k (MKT-20339)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…s (MKT-20338)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@snyk-io

snyk-io Bot commented Oct 30, 2026 •

Copy link
Copy Markdown

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

@github-actions

Copy link
Copy Markdown

🔒 Security Scan Results

ℹ️ Note: Only vulnerabilities with available fixes (upgrades or patches) are counted toward thresholds.

Check Type Count (with fixes) Without fixes Threshold Result
🔴 Critical Severity 0 0 10 ✅ Passed
🟠 High Severity 0 1 25 ✅ Passed
🟡 Medium Severity 0 0 500 ✅ Passed
🔵 Low Severity 0 0 1000 ✅ Passed

⏱️ SLA Breach Summary

✅ No SLA breaches detected. All vulnerabilities are within acceptable time thresholds.

Severity Breaches (with fixes) Breaches (no fixes) SLA Threshold (with/no fixes) Status
🔴 Critical 0 0 15 / 30 days ✅ Passed
🟠 High 0 0 30 / 120 days ✅ Passed
🟡 Medium 0 0 90 / 365 days ✅ Passed
🔵 Low 0 0 180 / 365 days ✅ Passed

ℹ️ Vulnerabilities Without Available Fixes (Informational Only)

The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:

  • Critical without fixes: 0
  • High without fixes: 1
  • Medium without fixes: 0
  • Low without fixes: 0

✅ BUILD PASSED - All security checks passed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants