Skip to content

DX-20927 | Back-merge master into development - #32

Merged
reeshika-h merged 7 commits into
developmentfrom
back-merge/DX-20927
Sep 29, 2026
Merged

reeshika-h merged 7 commits into
developmentfrom
back-merge/DX-20927

Conversation

@reeshika-h

Copy link
Copy Markdown
Contributor

Back-merge of the production branch into development to resolve branch divergence (mostly the CODEOWNERS update and workflow changes that landed on the production branch only).

Uses a dedicated back-merge/DX-20927 branch (production branch + development merged in) so the PR is up to date with development without modifying the production branch.

Jira: DX-20927

🤖 Generated with Claude Code

Aravind-Kumar-cstk and others added 6 commits June 19, 2026 12:55
Brings back-merge branch up to date with development so master can be back-merged cleanly (DX-20927).

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

snyk-io Bot commented Sep 24, 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 0 25 ✅ Passed
🟡 Medium Severity 0 0 0 ✅ Passed
🔵 Low Severity 0 0 0 ✅ 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

✅ BUILD PASSED - All security checks passed

The snyk/actions/gradle container has no Android SDK and its Gradle 8.5
init script fails, so snyk.json was never written. Set up JDK and the
Android SDK on the runner and run the Snyk CLI there instead.

Refs DX-20927

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@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 0 25 ✅ Passed
🟡 Medium Severity 0 2 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: 0
  • Medium without fixes: 2
  • Low without fixes: 0

✅ BUILD PASSED - All security checks passed

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot review overview

🟡 Changes recommended

The Android SDK package input is incorrectly formatted and will prevent the SCA workflow from reaching Snyk.

Review effort: Balanced
Findings: 1 High severity

Open (1)
What changed in this PR

Back-merges production branch governance and security workflow updates into development.

Changes:

  • Updates CODEOWNERS responsibilities.
  • Modernizes Snyk SCA setup and policy enforcement.
  • Removes automatic Jira issue creation.
File Description
CODEOWNERS Updates reviewer ownership patterns.
.github/​workflows/​sca-scan.yml Revises Android and Snyk scan setup.
.github/​workflows/​issues-jira.yml Removes Jira issue automation.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread .github/workflows/sca-scan.yml
@reeshika-h
reeshika-h merged commit 7cc624d into development Sep 29, 2026
11 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.

3 participants