[Snyk] Security upgrade @openapitools/openapi-generator-cli from 2.28.3 to 2.30.0

[sestinj]

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• packages/continue-sdk/package.json
• packages/continue-sdk/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Incorrect Authorization SNYK-JS-NESTJSCORE-15365922	803

---

Important

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

---

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

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Incorrect Authorization

---

Continue Tasks: ✅ 7 no changes — View all

---

Summary by cubic

Upgrade @openapitools/openapi-generator-cli to 2.30.0 in continue-sdk to fix a high-severity NestJS core authorization vulnerability and refresh transitive dependencies.

• Dependencies

  • Bump @openapitools/openapi-generator-cli from 2.28.3 to 2.30.0.
  • Pulls @nestjs/common and @nestjs/core to 11.1.14, addressing SNYK-JS-NESTJSCORE-15365922.
  • Updates transitive packages (e.g., glob 13.0.6, minimatch/minipass); CLI internals move from inquirer to @inquirer/select.

• Migration

  • The generator now requires Node >= 20.19.0. Update local and CI Node versions if needed.

^{Written for commit c8e64ee. Summary will update on new commits.}

[continue]

Documentation Review

No documentation updates are needed for this PR.

Reason: This is a security upgrade for an internal build tool dependency (@openapitools/openapi-generator-cli). The change:

• Only affects the lockfile and package.json version
• Is a build-time dependency, not user-facing
• Introduces no changes to APIs, configuration, or usage patterns
• Has no impact on how developers use or interact with Continue

Security dependency updates like this don't require documentation changes.

[cubic-dev-ai]

No issues found across 2 files