Skip to content

Conversation

@sestinj
Copy link
Contributor

@sestinj sestinj commented Nov 4, 2025

snyk-top-banner

Snyk has created this PR to upgrade vectordb from 0.4.20 to 0.21.2.

ℹ️ 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 76 versions ahead of your current version.

  • The recommended version was released 3 months ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-BABELHELPERS-9397697
452 Proof of Concept
medium severity Missing Release of Resource after Effective Lifetime
SNYK-JS-INFLIGHT-6095116
452 Proof of Concept
Release notes
Package name: vectordb
  • 0.21.2 - 2025-07-25
  • 0.21.2-beta.1 - 2025-07-22
  • 0.21.2-beta.0 - 2025-07-18
  • 0.21.1 - 2025-07-10
  • 0.21.1-beta.1 - 2025-07-09
  • 0.21.1-beta.0 - 2025-07-08
  • 0.21.0 - 2025-06-20
  • 0.20.1-beta.2 - 2025-06-19
  • 0.20.1-beta.1 - 2025-06-18
  • 0.20.1-beta.0 - 2025-06-16
  • 0.20.0 - 2025-06-04
  • 0.20.0-beta.2 - 2025-06-04
  • 0.20.0-beta.1 - 2025-06-03
  • 0.20.0-beta.0 - 2025-05-31
  • 0.19.2-beta.0 - 2025-05-23
  • 0.19.1 - 2025-05-22
  • 0.19.1-beta.5 - 2025-05-16
  • 0.19.1-beta.4 - 2025-05-08
  • 0.19.1-beta.3 - 2025-05-06
  • 0.19.1-beta.2 - 2025-05-06
  • 0.19.1-beta.1 - 2025-04-29
  • 0.19.1-beta.0 - 2025-04-28
  • 0.19.0 - 2025-04-25
  • 0.19.0-beta.11 - 2025-04-25
  • 0.19.0-beta.10 - 2025-04-22
  • 0.19.0-beta.9 - 2025-04-21
  • 0.19.0-beta.8 - 2025-04-17
  • 0.19.0-beta.7 - 2025-04-15
  • 0.19.0-beta.6 - 2025-04-08
  • 0.19.0-beta.5 - 2025-04-04
  • 0.19.0-beta.4 - 2025-04-02
  • 0.19.0-beta.3 - 2025-04-02
  • 0.19.0-beta.2 - 2025-04-01
  • 0.19.0-beta.1 - 2025-04-01
  • 0.19.0-beta.0 - 2025-03-30
  • 0.18.3-beta.0 - 2025-03-28
  • 0.18.2 - 2025-03-26
  • 0.18.2-beta.0 - 2025-03-21
  • 0.18.1 - 2025-03-11
  • 0.18.0 - 2025-03-10
  • 0.18.0-beta.0 - 2025-02-26
  • 0.17.0 - 2025-02-26
  • 0.16.1-beta.3 - 2025-02-20
  • 0.16.1-beta.1 - 2025-02-11
  • 0.16.1-beta.0 - 2025-02-07
  • 0.16.0 - 2025-02-07
  • 0.15.1-beta.3 - 2025-02-01
  • 0.15.1-beta.2 - 2025-01-30
  • 0.15.0 - 2025-01-14
  • 0.15.0-beta.0 - 2025-01-10
  • 0.14.2-beta.0 - 2025-01-06
  • 0.14.1 - 2024-12-26
  • 0.14.1-beta.5 - 2024-12-13
  • 0.14.1-beta.4 - 2024-12-13
  • 0.14.1-beta.3 - 2024-12-11
  • 0.14.1-beta.2 - 2024-12-11
  • 0.14.1-beta.1 - 2024-12-09
  • 0.14.1-beta.0 - 2024-12-09
  • 0.14.0 - 2024-12-06
  • 0.13.0 - 2024-11-15
  • 0.13.0-beta.1 - 2024-11-06
  • 0.13.0-beta.0 - 2024-11-06
  • 0.12.0 - 2024-10-29
  • 0.11.1-beta.1 - 2024-10-23
  • 0.11.1-beta.0 - 2024-10-17
  • 0.11.0 - 2024-10-09
  • 0.11.0-beta.1 - 2024-09-24
  • 0.11.0-beta.0 - 2024-09-19
  • 0.10.0 - 2024-09-10
  • 0.10.0-beta.1 - 2024-08-23
  • 0.10.0-beta.0 - 2024-08-12
  • 0.9.0 - 2024-08-07
  • 0.8.0 - 2024-07-26
  • 0.7.2 - 2024-07-23
  • 0.7.1 - 2024-07-17
  • 0.5.0 - 2024-05-23
  • 0.4.20 - 2024-05-09
from vectordb 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:


Summary by cubic

Upgrades vectordb from 0.4.20 to 0.21.2 to address security alerts and keep the vector DB client current. Includes fixes for ReDoS (SNYK-JS-BABELHELPERS-9397697) and a resource leak (SNYK-JS-INFLIGHT-6095116).

  • Dependencies
    • Bump vectordb in core/package.json to ^0.21.2.

Written for commit 75133e4. Summary will update automatically on new commits.

Snyk has created this PR to upgrade vectordb from 0.4.20 to 0.21.2.

See this package in npm:
vectordb

See this project in Snyk:
https://app.snyk.io/org/continue-dev-inc.-default/project/27a1a273-81ac-40fc-9af7-ac9cf0349aff?utm_source=github&utm_medium=referral&page=upgrade-pr
@sestinj sestinj requested a review from a team as a code owner November 4, 2025 07:36
@sestinj sestinj requested review from RomneyDa and removed request for a team November 4, 2025 07:36
@dosubot dosubot bot added the size:XS This PR changes 0-9 lines, ignoring generated files. label Nov 4, 2025
@github-actions
Copy link

github-actions bot commented Nov 4, 2025

⚠️ 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 Nov 4, 2025

✅ 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.

No issues found across 1 file

@RomneyDa RomneyDa closed this Nov 7, 2025
@github-project-automation github-project-automation bot moved this from Todo to Done in Issues and PRs Nov 7, 2025
@github-actions github-actions bot locked and limited conversation to collaborators Nov 7, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

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