feat: migrate from poetry to uv - support upcoming uv-first algokit version#112
Open
aorumbayev wants to merge 7 commits intoprep/beta-releasefrom
Open
feat: migrate from poetry to uv - support upcoming uv-first algokit version#112aorumbayev wants to merge 7 commits intoprep/beta-releasefrom
aorumbayev wants to merge 7 commits intoprep/beta-releasefrom
Conversation
|
Can we change the target branch from |
Collaborator
Author
|
@p2arthur whats the purpose of prep/beta-release - the decoupling/remove-algosdk was this repo's 'decoupling/alpha' branch - does prep/beta-release contain the changes from ? decoupling/remove-algosdk. If yes we should close the decoupling/remove-algosdk remove it and ill retarget this pr against prep/beta-release |
|
@aorumbayev Yeah, it is the |
aorumbayev
changed the base branch from
decoupling/remove-algosdk
to
prep/beta-release
- Convert pyproject.toml from Poetry to uv/hatchling build system - Replace poetry.lock with uv.lock - Remove poetry.toml configuration - Add [tool.uv] and [tool.hatch.metadata] sections
- Rewrite pyproject.toml.jinja from Poetry to uv/hatchling format - Cap requires-python to >=3.12,<3.14 (coincurve lacks 3.14 wheels) - Replace all 'poetry run' with 'uv run' in .algokit.toml.jinja - Bump min_version to v2.11.0 (old CLIs warn on version mismatch) - Simplify audit description (remove poetry-plugin-export reference) - Update CI/CD templates: astral-sh/setup-uv@v5, uv tool install algokit - Update pre-commit hooks: poetry run -> uv run - Update README.md.jinja: uv install guide, version references - Delete template_content/poetry.toml
- Update PY_PKG_MGR_ARGS from poetry to uv in both test files - Tests now configure generated projects to use uv as package manager
Auto-regenerated by running test_templates.py and test_generators.py against the updated template with algokit-cli decoupling branch. Changes across all examples: - .algokit.toml: min_version v2.11.0, poetry run -> uv run - pyproject.toml: Poetry format -> uv/hatchling with [project], [dependency-groups], [tool.hatch.metadata], [tool.uv] - README.md: Poetry -> uv install guide and tool references - poetry.toml: deleted - uv.lock: added (replaces Poetry lock) Production examples additionally: - .pre-commit-config.yaml: poetry run -> uv run - CI/CD workflows: astral-sh/setup-uv@v5, uv tool install algokit
- Add npm install step in check_codebase for TypeScript deployment projects (package.json present) to install @algorandfoundation/ algokit-client-generator before build - Patch jest.config.ts at test time to handle ESM node_modules: extend transform to cover .js files and add transformIgnorePatterns for @noble/hashes and @algorandfoundation packages (upstream generator template produces config without ESM support) All 6 tests now pass: 2 template + 4 generator (python+typescript × starter+production)
The Python template no longer offers TypeScript as a deployment language. All TS deployer files, TS jest test scaffolding, generated TS examples, and the deployment_language/use_typescript_jest copier questions have been removed. The template now generates Python-only deployer code.
aorumbayev
force-pushed
the
feat/uv-as-default
branch
from
fc8f8f2 to
325b1e9
Compare
Collaborator
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed Changes
Follow up to algorandfoundation/algokit-cli#712
deployment_languageanduse_typescript_jestcopier questions, all TS deployer/jest template files, generated TS examples, and every related conditional across.algokit.toml,__main__.py, README, VSCode/JetBrains configs, and tests have been deleted. The Python template now only generates Python deployment code.