Remove uv-ship and create justfile #14
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/issue-9-justfile"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Replaces the custom
uv-shiprelease tool with:bump-my-version(calver-compatible, mirrors the approach used incang)justfilewith areleaserecipe that handles changelog generation, version bump, tagging, and pushRemoves:
uv-shipfrom[dependency-groups] dev[tool.uv.sources]section[tool.uv-ship]sectionAdds:
bump-my-version~=1.5.1to[dependency-groups] dev[tool.bumpversion]config (calver parse/serialize, updatespyproject.toml)justfilewithreleaserecipeCloses #13
WuMing
Found 1 issue(s). See inline comments below.
@ -56,3 +56,2 @@[tool.uv.sources]uv-ship = { git = "https://github.com/marvin8/uv-ship-calver.git", branch = "calver" }[tool.bumpversion]config [HIGH]
The PR description states this config adds 'calver parse/serialize', but the [tool.bumpversion] section does not define the required
parseandserializeoptions. Without them, bump-my-version falls back to default semver versioning (e.g., bumping 0.4.0 to 0.4.1 instead of a calver version). To use calver, add appropriateparseandserializepatterns (and possiblycalver_format), and ensurecurrent_versionmatches the calver format.pyproject.tomlposition 0✅ Fixed in commit
a850615— addedparseandserializeto[tool.bumpversion]for calver year.month.day format.This PR is too large to review automatically (2057 lines; limit is 2000). Please consider splitting it into smaller PRs.
This PR is too large to review automatically (2177 lines; limit is 2000). Please consider splitting it into smaller PRs.
This PR is too large to review automatically (2177 lines; limit is 2000). Please consider splitting it into smaller PRs.