Feature Request

Description

• The current uv integration steps describe a way to sync the uv.lock file just before the PSR Action runs.
• This means that the uv.lock will remain out of sync most of the time, just that tiny moment when the build command is executed by the PSR Action, it will be in sync for the project version.
• Ref: https://python-semantic-release.readthedocs.io/en/latest/configuration/configuration-guides/uv_integration.html

Use cases

For those using uv and committing the uv.lock file to source. They would want the uv.lock file to be consistently in sync.

Possible implementation

• Add a option to sync the uv.lock file and that should update it right after semantic release and add or amend it to the same commit.
• Just like the build_command, have a post step to run any commands after the semantic release.

Alternative solutions

• Right now my solution for my project is to run a step in the main workflow that executes uv lock --upgrade-package <my_package_name> and then git add and commits the uv.lock file.
  • This steps runs right after the Semantic Version Release step.
  • My project links:
    • pyproject.toml: https://github.com/aqib-oss/sonar-qube-gh-action/blob/main/pyproject.toml
    • Merge to main workflow: https://github.com/aqib-oss/sonar-qube-gh-action/blob/main/.github/workflows/main-workflow.yaml