Skip to content

Fix v1 compat imports 2#277

Closed
xSAVIKx wants to merge 8 commits into
v2from
fix-v1-compat-imports-2
Closed

Fix v1 compat imports 2#277
xSAVIKx wants to merge 8 commits into
v2from
fix-v1-compat-imports-2

Conversation

@xSAVIKx
Copy link
Copy Markdown
Member

@xSAVIKx xSAVIKx commented Mar 22, 2026

Changes

  • Ensured that v1 compatibility layer still works. Moved tests to tests folder for v1 compatibility as well.
  • Added missing v1 compat dependencies
  • Updated migration guide mentioning the compatibility layer

One line description for the changelog

Fixed v1 compatibility layer

  • Tests pass
  • Appropriate changes to README are included in PR

xSAVIKx added 8 commits March 22, 2026 21:41
…1` to fix compatibility layer

Signed-off-by: Yurii Serhiichuk <savik.ne@gmail.com>
…t `>=2.0,<3.0` for v1 compat layer

Signed-off-by: Yurii Serhiichuk <savik.ne@gmail.com>
…r improved organization

Signed-off-by: Yurii Serhiichuk <savik.ne@gmail.com>
…sion constraints for libraries including `anyio`, `sanic`, `pydantic`, and others

Signed-off-by: Yurii Serhiichuk <savik.ne@gmail.com>
…ed `v1` modules for consistency

Signed-off-by: Yurii Serhiichuk <savik.ne@gmail.com>
…iles for consistency

Signed-off-by: Yurii Serhiichuk <savik.ne@gmail.com>
…y layer

Signed-off-by: Yurii Serhiichuk <savik.ne@gmail.com>
…, format protocol, and v2 API changes

Signed-off-by: Yurii Serhiichuk <savik.ne@gmail.com>
@xSAVIKx xSAVIKx self-assigned this Mar 22, 2026
@xSAVIKx xSAVIKx closed this Mar 22, 2026
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.

1 participant