Development - #188
Development#188aniket-shikhare-cstk wants to merge 8 commits into
Conversation
chore: back-merge main into development
chore: back-merge main into development
back merge
chore: back-merge main into development
… pattern
variants(x) treats its single positional arg as a branch UID, not a
variant UID, so variants("no_such_variant").fetch() left variant_uid=None
and hit the client-side ArgumentException guard before the HTTP call.
Fix: pass the UID to fetch() directly, which is the correct SDK pattern.
Generated by Claude Code
…nexistent fix(test): correct entry variants fetch_nonexistent to use fetch(uid) pattern
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
🔒 Security Scan Results
⏱️ SLA Breach Summary
ℹ️ 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:
✅ BUILD PASSED - All security checks passed |
Brings back-merge branch up to date with development so main can be back-merged cleanly (DX-20927). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
DX-20927 | Back-merge main into development
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
🔒 Security Scan Results
⏱️ SLA Breach Summary
✅ BUILD PASSED - All security checks passed |
Fixes the single failing test (test_fetch_nonexistent) in test_17_entry_variants.py that caused 269/270 on the last GoCD run
entry.variants(x) treats its single positional arg as a branch UID, not a variant UID — so .variants("no_such_variant").fetch() left variant_uid=None and hit the SDK's ArgumentException client-side guard before any HTTP call was made
Fix: .variants().fetch("no_such_variant") passes the UID to fetch() directly, which is the correct SDK pattern and reaches the server to get a 404/412/422 response