Repository navigation
fix: regenerate lock file and bump deps to resolve Snyk vulnerabilities (0.1.4) - #131
Merged
Merged
Conversation
- 18 dependency, devDependency, optionalDependency and override range changes in package.json - delete package-lock.json (and node_modules), then run a clean npm install to regenerate the lock file - patch version bump 0.1.3 -> 0.1.4 - Snyk (committed lock -> regenerated lock): 3 vulnerabilities -> 0 Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
✅ 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 |
reeshika-h
approved these changes
Nov 2, 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.
Summary
Clean lock file regeneration plus dependency bumps for
kickstart-angular, with a patch version bump, raised directly againstmainas requested. It carries the same changes as #130 (already merged intodevelopment), applied on top of the currentmain, which already includes #125.Version bump
package.jsonversionmaindevelopmentmain)The 0.1.4 bump is the version edit already made by hand in the working tree; it is above
main.What changed
package.json: version 0.1.3 -> 0.1.4 and 18 range changes across dependencies, devDependencies, optionalDependencies and overrides (for example@contentstack/delivery-sdk^5.5.2 -> ^5.6.2,@contentstack/live-preview-utils^4.4.5 -> ^4.5.3,tslib2.8.1 -> 2.9.1,zone.js~0.16.2 -> ~0.16.3,@angular-devkit/build-angular21.2.20 -> 21.2.29,@angular/cli21.2.26 -> 21.2.29,@types/react^19.2.18 -> ^19.3.0,postcss8.5.26 -> 8.5.32). These dependency edits were made by hand in the working tree before this run and are included as they were.package-lock.json: deleted together withnode_modules, then regenerated with a cleannpm install(lockfileVersion 3).Snyk (
snyk test, vulnerabilities only; licence findings listed separately)mainpackage.json, fresh lock)Fixed by the lock regeneration alone (3; 2 high, 1 medium): qs@6.16.0 (2): SNYK-JS-QS-20943482, SNYK-JS-QS-21755395; follow-redirects@1.16.1 (1): SNYK-JS-FOLLOWREDIRECTS-21762031
Fixed additionally by the
package.jsonbumps: none.Remaining vulnerabilities: none.
New vulnerabilities introduced: none.
Licence findings: 2 after (lightningcss-linux-x64-gnu MPL-2.0, lightningcss-linux-x64-musl MPL-2.0), 2 before.
Build and checks
mainas committednpm run buildThere is no
testscript in this repo.Run on Node v22.23.3 with the placeholder values from
.env.exampleas environment;npm installexit code 0. A failure that is identical onmainas committed is not caused by this change.Notes
package.jsonhere is identical to the one merged intodevelopmentby fix: regenerate lock file and bump deps to resolve Snyk vulnerabilities (0.1.4) #130.maincarries 5 commits thatdevelopmentlacked, including fix: bump 7 deps to resolve Snyk vulnerabilities #125 (7 dependency bumps); everypackage.jsonvalue fix: bump 7 deps to resolve Snyk vulnerabilities #125 changed is equal to or lower than the value in this PR, so this PR supersedes it.mainas committed (already improved by fix: bump 7 deps to resolve Snyk vulnerabilities #125), not the olderdevelopmentlock that fix: regenerate lock file and bump deps to resolve Snyk vulnerabilities (0.1.4) #130 started from.maindirectly.🤖 Generated with Claude Code