Skip to content

fix(skills): port remaining support-assistant fixes after 0.2.0 - #25

Merged
timbenniks-contentstack merged 2 commits into
nextfrom
fix/support-assistant-followups
Oct 23, 2026
Merged

timbenniks-contentstack merged 2 commits into
nextfrom
fix/support-assistant-followups

Conversation

@timbenniks-contentstack

Copy link
Copy Markdown
Contributor

Replaces #23, which came from a fork: the agent-scan and security-sca checks can't get repo secrets there, so they failed. This branch cherry-picks @hitesh-shetty-cstk's commit with his authorship intact, onto current next.

Changes

  • Hitesh's commit from fix(skills): port remaining support-assistant fixes after 0.2.0 #23, unchanged. See that PR for the eight fixes to cms-live-preview-visual-editor-support-assistant.
  • faq-preview-runtime.md: the third-party scripts entry still recommended Open in New Tab without scoping it to Live Preview. It now matches the rest of the PR: Live Preview only, since Visual Editor always renders in its canvas iframe.
  • CHANGELOG.md: added the fixes under 0.3.0.

Test plan

  • node scripts/validate.mjs passes (24 skills, 7 manifests, 0.3.0)
  • No other unscoped Open in New Tab recommendations in the skill

🤖 Generated with Claude Code

hitesh-shetty-cstk and others added 2 commits October 23, 2026 12:11
…erge

These were made on the original branch after it was folded into the
0.2.0 release, so they did not reach it:

- Open in New Tab is scoped to Live Preview; Visual Editor does not
  support it and always renders in its canvas iframe.
- Missing Visual Experience navigation checks the stack's Live Preview
  setting before treating it as provisioning.
- The CORS entry no longer rules out a Contentstack-side cause, and its
  verification says curl does not enforce CORS.
- GraphQL preview requests keep access_token and Content-Type.
- livePreviewQuery: live_preview is the only required key and an empty
  one resets the instance; both key spellings are accepted.
- The editButton exclude config applies only where init() runs.
- Cache guidance separates app and CDN caches from SDK caching and says
  the hash rotates on a timer rather than on edits.
- The framework examples say which stackSdk to pass per Delivery SDK.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…rty scripts; changelog

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@timbenniks-contentstack
timbenniks-contentstack requested a review from a team as a code owner October 23, 2026 10:12
@snyk-io

snyk-io Bot commented Oct 23, 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)
✅ 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

@timbenniks-contentstack
timbenniks-contentstack merged commit ea2eee3 into next Oct 23, 2026
7 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