Skip to content

fix(variables): split a variable at the first separator and raise when a stack lookup cannot finish - #249

Merged
Harshi-Shah-CS merged 1 commit into
v2-devfrom
cl-7761
Oct 22, 2026
Merged

Harshi-Shah-CS merged 1 commit into
v2-devfrom
cl-7761

Conversation

@Harshi-Shah-CS

Copy link
Copy Markdown
Contributor

What

Follow-up to the routine review of #245, #246 and #247. Three fixes; the other findings were checked and left alone.

  • Separator order — variable.parse now splits a KEY=value / KEY: value line at whichever of = and : comes first, so URL=http://x and A:b=c keep the value intact.
  • Page cap — allPages in the CMA client used to stop silently after 100 pages and return a partial list. It now raises CmaScanLimitError (a UsageError) naming what it was listing (stacks / delivery tokens).
  • AGENTS.md — states that an error code with no ENVIRONMENT_ERROR_MESSAGES entry falls back to the API's own message, and describes CmaScanLimitError.

Tests

Scoped tests, eslint and the full coverage run all pass: 138 suites, 2,379 tests, 100% statements / branches / functions / lines.

.talismanrc checksums are refreshed for the five touched files.

#claude_code#
🤖 Generated with Claude Code

…n a stack lookup cannot finish

Follow-up to review of #245 and #247.

parseAssignment now splits at whichever of "=" and ":" comes first, so a
value may hold the other one: API_URL:https://x.test?a=b is the key
API_URL and the whole URL, where it used to split at the later "=".

The stack and delivery-token lookups behind --from-stack stopped
silently after 100 pages and returned a truncated list. They now raise
CmaScanLimitError, as every other scan that cannot finish does.

AGENTS.md says what a code with no message entry falls back to, instead
of claiming a failed PATCH is never worded from the API's text.

#claude_code#
🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
Co-authored-by: Harshi Shah <harshi.shah@contentstack.com>
Co-authored-by: Sakshi Koli <sakshi.koli@contentstack.com>
@Harshi-Shah-CS
Harshi-Shah-CS requested a review from a team as a code owner October 22, 2026 09:39
@snyk-io

snyk-io Bot commented Oct 22, 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 9 25 ✅ Passed
🟡 Medium Severity 0 3 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: 9
  • Medium without fixes: 3
  • Low without fixes: 0

✅ BUILD PASSED - All security checks passed

@Harshi-Shah-CS Harshi-Shah-CS changed the title fix(variables): split a variable at the first separator and raise when a stack lookup cannot finish (+Claude) fix(variables): split a variable at the first separator and raise when a stack lookup cannot finish Oct 22, 2026
@Harshi-Shah-CS
Harshi-Shah-CS merged commit 205f368 into v2-dev Oct 22, 2026
7 checks passed
@Harshi-Shah-CS
Harshi-Shah-CS deleted the cl-7761 branch October 22, 2026 10:15
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.

4 participants