We are using uv to manage our Python packages and release-please to create our releases. The workflow that creates the new releases in GitHub currently does not update the version of our package in uv.lock. release-please currently updates the following files: .release-please-manifest.json CHANGELOG.md pyproject.toml It should additionally change the version number in: uv.lock Here's the release-please-config.yaml we are using: { "packages": { ".": { "package-name": "<OUR PACKAGE NAME>", "path": "src", "release-type": "python", "bump-minor-pre-major": true, "changelog-path": "CHANGELOG.md", "include-component-in-tag": false } }, "$schema": "https://raw.githubusercontent.com/googleapis/release-please/main/schemas/config.json" } Here is how we integrate it in our GitHub workflow: jobs: release-please: runs-on: [self-hosted, x64, linux, philips-code-hub, ubuntu-latest] outputs: releases_created: ${{ steps.release.outputs.releases_created }} release_created: ${{ steps.release.outputs.release_created }} release_id: ${{ steps.release.outputs.id }} release_name: ${{ steps.release.outputs.name }} release_tag_name: ${{ steps.release.outputs.tag_name }} release_sha: ${{ steps.release.outputs.sha }} release_body: ${{ steps.release.outputs.body }} release_html_url: ${{ steps.release.outputs.html_url }} release_draft: ${{ steps.release.outputs.draft }} release_upload_url: ${{ steps.release.outputs.upload_url }} release_path: ${{ steps.release.outputs.path }} release_version: ${{ steps.release.outputs.version }} release_major: ${{ steps.release.outputs.major }} release_minor: ${{ steps.release.outputs.minor }} release_patch: ${{ steps.release.outputs.patch }} release_pr_number: ${{ steps.release.outputs.prNumber }} paths_released: ${{ steps.release.outputs.paths_released }} prs_created: ${{ steps.release.outputs.prs_created }} steps: - name: release please uses: googleapis/release-please-action@a02a34c4d625f9be7cb89156071d8567266a2445 # ratchet:googleapis/release-please-action@v4 id: release with: token: ${{ secrets.GITHUB_TOKEN }} config-file: release-please-config.json manifest-file: .release-please-manifest.json We could now introduce another step that updates uv.lock and creates another commit - but ideally, changes needed for a release to all necessary files should be kept together in one commit. What we tried already (according to the documentation) is adding the uv.lock to the extra-files in the release-please-config.json - but that also didn't help. Continue reading...
