⚠ This page is served via a proxy. Original site: https://github.com
This service does not collect credentials or authentication data.
Skip to content

Conversation

@sestinj
Copy link
Contributor

@sestinj sestinj commented Jan 13, 2026

snyk-top-banner

Snyk has created this PR to upgrade lru-cache from 11.0.2 to 11.2.4.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 6 versions ahead of your current version.

  • The recommended version was released a month ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
high severity Command Injection
SNYK-JS-GLOB-14040952
436 Proof of Concept
medium severity Prototype Pollution
SNYK-JS-JSYAML-13961110
436 No Known Exploit
medium severity Directory Traversal
SNYK-JS-VITE-13644406
436 Proof of Concept
low severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-BRACEEXPANSION-9789073
436 Proof of Concept
low severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-BRACEEXPANSION-9789073
436 Proof of Concept
low severity Relative Path Traversal
SNYK-JS-VITE-12558116
436 Proof of Concept
Release notes
Package name: lru-cache from lru-cache GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:


Continue Tasks

Status Task Actions
▶️ Queued Create GitHub Issue (OS) View
▶️ Queued Update PostHog Dashboards View

Powered by Continue


Summary by cubic

Upgrade lru-cache from 11.0.2 to 11.2.4 in the VS Code extension to pick up recent fixes and improvements. Updated package.json and package-lock.json; no app code modified.

Written for commit ca5d945. Summary will update on new commits.

Snyk has created this PR to upgrade lru-cache from 11.0.2 to 11.2.4.

See this package in npm:
lru-cache

See this project in Snyk:
https://app.snyk.io/org/continue-dev-inc.-default/project/7ff64b12-9373-49d8-a6a5-70de1609223c?utm_source=github&utm_medium=referral&page=upgrade-pr
@sestinj sestinj requested a review from a team as a code owner January 13, 2026 08:41
@sestinj sestinj requested review from RomneyDa and removed request for a team January 13, 2026 08:41
@continue-staging
Copy link

All Green - Keep your PRs mergeable

Learn more

All Green is an AI agent that automatically:

✅ Addresses code review comments

✅ Fixes failing CI checks

✅ Resolves merge conflicts


Unsubscribe from All Green comments

@continue
Copy link
Contributor

continue bot commented Jan 13, 2026

All Green - Keep your PRs mergeable

Learn more

All Green is an AI agent that automatically:

✅ Addresses code review comments

✅ Fixes failing CI checks

✅ Resolves merge conflicts


Unsubscribe from All Green comments

@dosubot dosubot bot added the size:XS This PR changes 0-9 lines, ignoring generated files. label Jan 13, 2026
@github-actions
Copy link

⚠️ PR Title Format

Your PR title doesn't follow the conventional commit format, but this won't block your PR from being merged. We recommend using this format for better project organization.

Expected Format:

<type>[optional scope]: <description>

Examples:

  • feat: add changelog generation support
  • fix: resolve login redirect issue
  • docs: update README with new instructions
  • chore: update dependencies

Valid Types:

feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert

This helps with:

  • 📝 Automatic changelog generation
  • 🚀 Automated semantic versioning
  • 📊 Better project history tracking

This is a non-blocking warning - your PR can still be merged without fixing this.

@github-actions
Copy link

github-actions bot commented Jan 13, 2026

✅ Review Complete

Code Review Summary

⚠️ Continue API authentication failed. Please check your CONTINUE_API_KEY.


Copy link
Contributor

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1 issue found across 1 file

Prompt for AI agents (all issues)

Check if these issues are valid — if so, understand the root cause of each and fix them.


<file name="extensions/vscode/package.json">

<violation number="1" location="extensions/vscode/package.json:754">
P2: lru-cache upgrade in package.json not reflected in package-lock.json; lockfile still pins 11.0.2 so the bump won’t apply</violation>
</file>

Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.

@github-project-automation github-project-automation bot moved this from Todo to In Progress in Issues and PRs Jan 13, 2026
@dosubot dosubot bot added the lgtm This PR has been approved by a maintainer label Jan 13, 2026
@RomneyDa RomneyDa merged commit edcba3e into main Jan 13, 2026
58 checks passed
@github-project-automation github-project-automation bot moved this from In Progress to Done in Issues and PRs Jan 13, 2026
@RomneyDa RomneyDa deleted the snyk-upgrade-82ccb8a196b4b54a9e7ed15248f19fcf branch January 13, 2026 23:38
@github-actions github-actions bot locked and limited conversation to collaborators Jan 13, 2026
@sestinj
Copy link
Contributor Author

sestinj commented Jan 14, 2026

🎉 This PR is included in version 1.37.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@sestinj
Copy link
Contributor Author

sestinj commented Jan 15, 2026

🎉 This PR is included in version 1.39.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

lgtm This PR has been approved by a maintainer released size:XS This PR changes 0-9 lines, ignoring generated files.

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

4 participants