We should clean up the number of PRs -- namely the security-related nones -- by closing the automated Snyk pulls. Below I have compiled a list of the PRs that can be left opened (and merged), should be closed (duplicates), and those that require more investigation.
After these merge, we should do a final CVE check to see if any lingering, resolvable CVEs exist.
Can be kept... (5 + 1)
Can be closed... (19)
Ideal // Investigation Needed (2)
Here due to breaking changes requiring more investigation...
These would be the ideal versions, as opposed to above, but there were notes in the PRs regarding breaking changes requiring more investigation.
We should clean up the number of PRs -- namely the security-related nones -- by closing the automated Snyk pulls. Below I have compiled a list of the PRs that can be left opened (and merged), should be closed (duplicates), and those that require more investigation.
After these merge, we should do a final CVE check to see if any lingering, resolvable CVEs exist.
Can be kept... (5 + 1)
js-yaml: 4.1.0 -> 4.3.1. This was done in some PRs (e.g. [Snyk] Fix for 1 vulnerabilities #105), but those also had bumps topuppeteerwhich is already handled above to a newer version.Can be closed... (19)
@qdrant/js-client-rest: 1.13.0 -> 1.14.1@qdrant/qdrant-js: 1.13.0 -> 1.14.1@qdrant/js-client-rest: 1.13.0 -> 1.14.1@qdrant/qdrant-js: 1.13.0 -> 1.14.1js-yaml: 4.1.0 -> 4.3.1puppeteer: 24.1.1 -> 24.15.0js-yaml: 4.1.0 -> 4.3.0puppeteer: 24.1.1 -> 24.15.0js-yaml: 4.1.0 -> 4.2.0puppeteer: 24.1.1 -> 24.15.0axios: 1.6.2 -> 1.13.2puppeteer: 24.1.1 -> 24.15.0Ideal // Investigation Needed (2)
Here due to breaking changes requiring more investigation...
These would be the ideal versions, as opposed to above, but there were notes in the PRs regarding breaking changes requiring more investigation.