Repository navigation
build(python): one version source so release PRs keep uv.lock fresh - #27
Merged
Merged
Conversation
…allow the main scope in PR titles release-please raised project.version in pyproject.toml, but uv.lock also recorded the version, so uv sync --locked failed on the release PR and would have failed on main after the release. The version is now dynamic (read from src/bitpin_sdk/__init__.py, which release-please already updates), and uv.lock no longer stores it. release-please titles its PRs chore(main): ...; the PR-title check now accepts the main scope. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
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
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.
Fixes the CI failures on the release PRs #14 and #16.
uv.lockon Python releases (chore(main): release python 0.2.0 #14).versioninpyproject.toml, butuv.lockrecords it too, souv sync --lockedfailed on every job. After the release merged it would have failed onmainas well.src/bitpin_sdk/__init__.py, which release-please already updates throughx-release-please-version.uv.lockno longer stores the project version.uv lock --checkstays green after a version bump; the build produces the right version; release-please's pyproject updater handles the dynamic version without errors.chore(main): release …, and the check now allows themainscope.build, so no new release. After this merges, release-please rebuilds #14 without the lock problem.🤖 Generated with Claude Code