chore: migrate to uv package manager

Author: vdusek

.github/workflows/build_and_deploy_docs.yaml

@@ -54,10 +54,13 @@ jobs:
         with:
           python-version: ${{ env.PYTHON_VERSION }}
 
+      - name: Install uv package manager
+        uses: astral-sh/setup-uv@v5
+        with:
+          python-version: ${{ env.PYTHON_VERSION }}
+
       - name: Install Python dependencies
-        run: |
-          pipx install --python ${{ env.PYTHON_VERSION }} poetry
-          make install-dev
+        run: make install-dev
 
       - name: Build generated API reference
         run: make build-api-reference

.gitignore

@@ -10,9 +10,6 @@ __pycache__
 .envrc
 .python-version
 
-# Poetry
-poetry.toml
-
 # Mise
 mise.toml
 .mise.toml

CONTRIBUTING.md

@@ -6,7 +6,7 @@ Here you'll find a contributing guide to get started with development.
 
 For local development, it is required to have Python 3.9 (or a later version) installed.
 
-We use [Poetry](https://python-poetry.org/) for project management. Install it and set up your IDE accordingly.
+We use [uv](https://docs.astral.sh/uv/) for project management. Install it and set up your IDE accordingly.
 
 ## Dependencies
 
@@ -134,33 +134,33 @@ Publishing new versions to [PyPI](https://pypi.org/project/apify) is automated t
 
 ### Publishing to PyPI manually
 
-1. **Do not do this unless absolutely necessary.** In all conceivable scenarios, you should use the `release` workflow instead.
+1. **Do not do this unless absolutely necessary.** In all conceivable scenarios, you should use the `run_release` workflow instead.
 2. **Make sure you know what you're doing.**
 
 3. Update the version number:
 
-- Modify the `version` field under `tool.poetry` in `pyproject.toml`.
+- Modify the `version` field under `project` in `pyproject.toml`.
 
 ```toml
-[tool.poetry]
-name = "apify"
+[project]
+name = "crawlee"
 version = "x.z.y"
 ```
 
 4. Generate the distribution archives for the package:
 
 ```shell
-poetry build
+uv build
 ```
 
 5. Set up the PyPI API token for authentication:
 
 ```shell
-poetry config pypi-token.pypi YOUR_API_TOKEN
+uv config pypi-token.pypi YOUR_API_TOKEN
 ```
 
 6. Upload the package to PyPI:
 
 ```shell
-poetry publish
+uv publish
 ```

Makefile

@@ -1,5 +1,4 @@
-.PHONY: clean install-dev build publish-to-pypi lint type-check unit-tests unit-tests-cov \
-		integration-tests format check-code build-api-reference build-docs run-docs
+.PHONY: clean install-dev build publish-to-pypi lint type-check unit-tests unit-tests-cov integration-tests format check-code build-api-reference run-docs
 
 # This is default for local testing, but GitHub workflows override it to a higher value in CI
 INTEGRATION_TESTS_CONCURRENCY = 1
@@ -8,46 +7,45 @@ clean:
 	rm -rf .mypy_cache .pytest_cache .ruff_cache build dist htmlcov .coverage
 
 install-dev:
-	poetry install --all-extras
-	poetry run pre-commit install
+	uv sync --all-extras
+	uv run pre-commit install
 
 build:
-	poetry build --no-interaction -vv
+	uv build --no-cache
 
 # APIFY_PYPI_TOKEN_CRAWLEE is expected to be set in the environment
 publish-to-pypi:
-	poetry config pypi-token.pypi "${APIFY_PYPI_TOKEN_CRAWLEE}"
-	poetry publish --no-interaction -vv
+	uv publish --token "${APIFY_PYPI_TOKEN_CRAWLEE}"
 
 lint:
-	poetry run ruff format --check
-	poetry run ruff check
+	uv run ruff format --check
+	uv run ruff check
 
 type-check:
-	poetry run mypy
+	uv run mypy
 
 unit-tests:
-	poetry run pytest --numprocesses=auto --verbose --cov=src/apify tests/unit
+	uv run pytest --numprocesses=auto --verbose --cov=src/crawlee tests/unit
 
 unit-tests-cov:
-	poetry run pytest --numprocesses=auto --verbose --cov=src/apify --cov-report=html tests/unit
+	uv run pytest --numprocesses=auto --verbose --cov=src/crawlee --cov-report=html tests/unit
 
 integration-tests:
-	poetry run pytest --numprocesses=$(INTEGRATION_TESTS_CONCURRENCY) --verbose tests/integration
+	uv run pytest --numprocesses=$(INTEGRATION_TESTS_CONCURRENCY) tests/integration
 
 format:
-	poetry run ruff check --fix
-	poetry run ruff format
+	uv run ruff check --fix
+	uv run ruff format
 
 # The check-code target runs a series of checks equivalent to those performed by pre-commit hooks
 # and the run_checks.yaml GitHub Actions workflow.
 check-code: lint type-check unit-tests
 
 build-api-reference:
-	cd website && poetry run ./build_api_reference.sh
+	cd website && uv run ./build_api_reference.sh
 
 build-docs:
-	cd website && poetry run npm clean-install && poetry run npm run build
+	cd website && corepack enable && yarn && uv run yarn build
 
 run-docs: build-api-reference
-	cd website && poetry run npm clean-install && poetry run npm run start
+	cd website && corepack enable && yarn && uv run yarn start