mirror of
https://github.com/aiogram/aiogram.git
synced 2026-04-08 16:37:47 +00:00
Migrate to UV (#1748)
* Switch to using `uv` for dependency management and update related project workflows and scripts * Expand contributing documentation with instructions for using `uv`, including dependency management, testing, linting, and docs workflows. * Add changelog entry for migration to `uv` for dependency management and workflows
This commit is contained in:
parent
7201e82238
commit
ce4ddb77f4
9 changed files with 3203 additions and 149 deletions
21
CHANGES/1748.misc.rst
Normal file
21
CHANGES/1748.misc.rst
Normal file
|
|
@ -0,0 +1,21 @@
|
|||
Migrated from ``hatch`` to ``uv`` for dependency management and development workflows.
|
||||
|
||||
This change improves developer experience with significantly faster dependency resolution (10-100x faster than pip), automatic virtual environment management, and reproducible builds through lockfile support.
|
||||
|
||||
**What changed for contributors:**
|
||||
|
||||
- Install dependencies with ``uv sync --all-extras --group dev --group test`` instead of ``pip install -e .[dev,test,docs]``
|
||||
- Run commands with ``uv run`` prefix (e.g., ``uv run pytest``, ``uv run black``)
|
||||
- All Makefile commands now use ``uv`` internally (``make install``, ``make test``, ``make lint``, etc.)
|
||||
- Version bumping now uses a custom ``scripts/bump_version.py`` script instead of ``hatch version``
|
||||
|
||||
**What stayed the same:**
|
||||
|
||||
- Build backend remains ``hatchling`` (no changes to package building)
|
||||
- Dynamic version reading from ``aiogram/__meta__.py`` still works
|
||||
- All GitHub Actions CI/CD workflows updated to use ``uv``
|
||||
- ReadTheDocs builds continue to work without changes
|
||||
- Development dependencies (``dev``, ``test``) moved to ``[dependency-groups]`` section
|
||||
- Documentation dependencies (``docs``) remain in ``[project.optional-dependencies]`` for compatibility
|
||||
|
||||
Contributors can use either the traditional ``pip``/``venv`` workflow or the new ``uv`` workflow - both are documented in the contributing guide.
|
||||
Loading…
Add table
Add a link
Reference in a new issue