Skip to content

Fix: Spring pins and hardcoded test values (Snyk) - v2.8.3 - #315

Merged
reeshika-h merged 313 commits into
masterfrom
fix/snyk-java-deps-and-credentials
Nov 2, 2026
Merged

reeshika-h merged 313 commits into
masterfrom
fix/snyk-java-deps-and-credentials

Conversation

@reeshika-h

Copy link
Copy Markdown
Contributor

Summary

Resolves DX-10363 to DX-10367 (Spring Framework vulnerabilities) and DX-22028, DX-22029 (hardcoded credentials in tests), v2.8.3.

  • dependencyManagement pins for spring-core, spring-beans, spring-web 6.2.19 → 7.0.9 (the version contentstack-utils already targets). These are build-time pins and do not propagate to consumers.
  • TestEntryModel: the two hardcoded publisher values are generated UUIDs (the assert uses the same variable); removed the deepcode ignore comments.

Verification

  • snyk test: 5 → 0; snyk code test: 2 → 0.
  • Tests: 1382/1382 pass (same as baseline).

🤖 Generated with Claude Code

Aravind-Kumar-cstk and others added 30 commits April 16, 2025 10:37
- Introduced SanityReport class to generate test summaries and send reports to Slack.
- Updated logging in CSHttpConnection to use logger instead of printStackTrace.
- Modified error handling in Entry class to check for empty error messages.
- Updated dependency versions in pom.xml and added new dependencies.
- Added test configuration properties to .gitignore.
- Created send-report.sh script for running tests and sending reports.
Fixed testcase assertions to be env agnostic
Update version to 2.1.1 and updated changelog
Update branch restrictions in PR workflow and add Talisman configuration
reeshika-h and others added 11 commits July 3, 2026 14:52
fix: update version to 2.7.2 and add Snyk fixes to CHANGELOG
…anch headers

Addresses Copilot review on PR #295:
- Guard variants(String) and variants(String[]) against null input
- Treat whitespace-only variant/branch as blank via trim().isEmpty()
- Join multi-variant header with "," for consistency with other SDK headers

Blank input intentionally skips (does not remove) the header: headers are a
shared Stack-level map, so remove() would clear the header for sibling
Entry/Query objects and the Stack-level default.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…-support

Add variant and branch support in Entry and Query APIs
chore: back-merge master into development
The secret-removal history rewrite on master left development on the old,
pre-rewrite commit SHAs. Every development-only commit is a content-identical
copy of a master commit (same tree and message, only the GPG signature differs),
so this merge records development as a parent while keeping master's tree
unchanged. That gives the two branches a shared merge-base again.

Refs DX-20927

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
DX-20927 | Back-merge master into development (reconcile rewritten history)
Build-time Spring pins 6.2.19 -> 7.0.9; replace hardcoded publisher values in tests with generated UUIDs; v2.8.3.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@reeshika-h
reeshika-h requested a review from a team as a code owner October 26, 2026 10:55
@snyk-io

snyk-io Bot commented Oct 26, 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 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

✅ BUILD PASSED - All security checks passed

cs-raj
cs-raj previously approved these changes Oct 30, 2026
@reeshika-h
reeshika-h changed the base branch from development to master November 2, 2026 05:57
@reeshika-h
reeshika-h dismissed cs-raj’s stale review November 2, 2026 05:57

The base branch was changed.

@github-actions

github-actions Bot commented Nov 2, 2026

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

✅ BUILD PASSED - All security checks passed

The job posts a coverage comment on the PR and the step fails with
"Resource not accessible by integration" because the token is read-only.
Declare the permissions the job needs, as the js-core and typescript
coverage workflows already do.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@reeshika-h
reeshika-h requested a review from a team as a code owner November 2, 2026 06:30
@github-actions

github-actions Bot commented Nov 2, 2026

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

✅ BUILD PASSED - All security checks passed

@github-actions

github-actions Bot commented Nov 2, 2026

Copy link
Copy Markdown

Coverage Summary

  • 📘 Instruction Coverage: 93%
  • 🌿 Branch Coverage: 80%

cs-raj
cs-raj previously approved these changes Nov 2, 2026
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@github-actions

github-actions Bot commented Nov 2, 2026

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

✅ BUILD PASSED - All security checks passed

@reeshika-h
reeshika-h merged commit cebaeb4 into master Nov 2, 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.

9 participants