Repository navigation
Restore lockfile platform packages for the v1.11.4 publish and Add ggshield secret scan to husky hooks - #271
Merged
Merged
Conversation
Update deployment logs query to V2, Add rollback plan-not-available message and Upgrade cli-utilities with Snyk fixes
…s-scan workflow (+Claude) GitGuardian's remote GitHub check already scans every PR, so the secrets-scan.yml workflow is redundant; remove it and its .talismanrc entry. Add Contentstack Security's standard ggshield block to the top of .husky/pre-commit and .husky/pre-push. launch-cli is public, so a missing ggshield warns instead of blocking; a secret ggshield finds still blocks. pre-push reads the pushed refs once and pipes them to both ggshield and secrets-scan.sh, since each reads stdin and the second would otherwise get nothing and skip the Talisman/trufflehog scan. Both hook files get a .talismanrc checksum: Talisman flags the setup-URL warning line. #claude_code# 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
chore(hooks): add ggshield secret scan to husky hooks and drop secrets-scan workflow
…k.json The v1.11.4 publish workflow failed at `npm ci`: npm 11 (Node 24 in CI) reported 50 packages missing from the lockfile - the per-platform builds of rollup and @unrs/resolver-binding. npm 10 tolerates the gap, so local installs and PR checks never caught it. #226 had restored these entries on main, but the main -> development sync for this release kept development's lockfile and dropped them. Regenerated with `npm install --package-lock-only` on npm 11. The change only adds the missing entries; no package is removed or re-versioned. #claude_code# 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
fix(deps): restore platform-specific optional packages in package-lock.json
✅ 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 |
AryanBansal-launch
approved these changes
Oct 30, 2026
siddharth-kulkarni-cs
approved these changes
Oct 30, 2026
Aravind-Kumar-cstk
approved these changes
Oct 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fix(deps): restore platform-specific optional packages in package-lock.json (#270)
chore(hooks): add ggshield secret scan to husky hooks and drop secrets-scan workflow (#267)
chore: Sync main into staging (#266 release merge commit)