mirror of https://github.com/hwchase17/langchain.git synced 2026-04-04 19:35:08 +00:00

Files

John Kennedy 0f4f3f74c8 chore: pygments>=2.20.0 across all packages (CVE-2026-4539) (#36385 )

## Summary

Bumps `pygments` to `>=2.20.0` across all 21 affected packages to
address [CVE-2026-4539](https://github.com/advisories/GHSA-XXXX) — ReDoS
via inefficient GUID regex in Pygments.

- **Severity:** Low
- **Fixed in:** 2.20.0 (was 2.19.2)
- **Change:** Added `pygments>=2.20.0` to `constraint-dependencies` in
`[tool.uv]` for each package, then ran `uv lock --upgrade-package
pygments` to regenerate lock files.

Closes Dependabot alerts #3435–#3455.

## Release Note
Patch deps

### Test Plan
 - [x] CI Green 🙏

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-03-30 23:26:59 -04:00

langchain_perplexity

fix(core,model-profiles): add missing ModelProfile fields, warn on schema drift (#36129 )

2026-03-23 00:44:27 -04:00

scripts

ci: avoid unnecessary dep installs in lint targets (#36046 )

2026-03-17 21:23:29 -04:00

tests

feat(perplexity): overhaul integration with official SDK and Search API (#34412 )

2025-12-19 12:58:41 -05:00

.gitignore

…

LICENSE

…

Makefile

ci: suppress pytest streaming output in CI (#36092 )

2026-03-18 21:24:47 -04:00

pyproject.toml

chore: pygments>=2.20.0 across all packages (CVE-2026-4539) (#36385 )

2026-03-30 23:26:59 -04:00

README.md

chore: update twitter URLs (#34736 )

2026-01-13 01:54:11 -05:00

uv.lock

chore: pygments>=2.20.0 across all packages (CVE-2026-4539) (#36385 )

2026-03-30 23:26:59 -04:00

README.md

langchain-perplexity

Looking for the JS/TS version? Check out LangChain.js.

Quick Install

pip install langchain-perplexity

🤔 What is this?

This package contains the LangChain integration with Perplexity.

📖 Documentation

For full documentation, see the API reference. For conceptual guides, tutorials, and examples on using these classes, see the LangChain Docs.

📕 Releases & Versioning

See our Releases and Versioning policies.

💁 Contributing

As an open-source project in a rapidly developing field, we are extremely open to contributions, whether it be in the form of a new feature, improved infrastructure, or better documentation.

For detailed information on how to contribute, see the Contributing Guide.