Skip to content

Conversation

mdrxy
Copy link
Contributor

@mdrxy mdrxy commented Aug 28, 2025

No description provided.

mdrxy and others added 6 commits August 27, 2025 21:32
Spring cleaning!

> [!WARNING]
> Python 3.9 dropped - Users on Python 3.9 must upgrade to Python 3.10+

## Infra / devx / env
* Poetry → UV Migration
  * Complete replacement of Poetry
  * Migrated CI workflows
  * Updated all build commands / `make` targets
* Dropped Python `3.9` support, minimum version now `>=3.10`
  * Removed Python `3.9` from CI test matrices
* Upgraded ruff to `>=0.12.10` and mypy to `>=1.17.1`
* Fixed hundreds of linting warnings to reduce noise
* Applied consistent formatting and style fixes
* Removed codespell
* Updated all Jupyter notebooks to reflect latest API patterns
  * Formatted all notebook cells with ruff
* Consistent markdown formatting across README files resolving
markdownlint warnings

(Sorry for the formatting noise)

No breaking functional changes other than language support
Lint v.1.0.0 branch post 9/3 upstream merge
@michaelnchin
Copy link
Collaborator

Hi @mdrxy, could you grant me permissions to push directly to this branch? I'm trying resolve the merge conflicts with main, but I'm having some trouble getting it working when committing from a separate branch.

@michaelnchin
Copy link
Collaborator

michaelnchin commented Sep 23, 2025

Quick update - I've tried the opposite of before and rebased the v1.0.0 onto main, which worked better: michaelnchin#4

Changes are staged on this branch. If it's alright, I'm going open a separate PR from that branch with Mason attributed to the changes. Will add more details there, but our main motivation for a possible early merge is to:

  1. Make the uv support (for both langchain-aws and langgraph-checkpoint-aws, which has several incoming service integrations) available ahead of the v1 release
  2. Convert main to the staging branch for v1 changes. This should make v1.0.0a -> v1.0.0 prod change and release management simpler. A separate v0.2.x would be maintained and updated for prod releases up to the v1 launch.

@mdrxy
Copy link
Contributor Author

mdrxy commented Sep 23, 2025

@michaelnchin both sound good to me! apologies for missing the last message - been tied up with other packages at the moment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants