馃Ч migrate to uv - #121
Merged
Merged
Conversation
alexjrk
force-pushed
the
feature/migrate-to-uv
branch
from
July 31, 2025 11:53
b165423 to
1cea769
姣旇緝
alexjrk
force-pushed
the
feature/migrate-to-uv
branch
from
July 31, 2025 13:01
9c76c1e to
09f828a
姣旇緝
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
娉ㄥ唽 for free
to join this conversation on GitHub.
Already have an account?
鐧诲綍 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.
Migrate from poetry to uv: https://docs.astral.sh/uv/
Also removed
Check Markdown linksstep fromlint-docspipeline, as I couldn't find a suitable, up-to-date GitHub Action or library for it. The one we previously used produced many false positives, and I don't think this check is critical at the moment. I haven鈥檛 seen similar checks in other major libraries like FastAPI, UV, etc.Submitter checklist
#help-contributingor a project-specific channel like#wiremock-java