Purpose

• Documentation fix on how to update the uv lock file after new release
• Resolves: UV integration documentation examples do not work as intended #1280

Rationale

• I am using uv and PSR for my package: https://github.com/aqib-oss/sonar-qube-gh-action
• I looked at the uv documentation and found a command to upgrade the version of only one package. Since uv lock file has the version of your project as well, I found that the command can be used to have the version synced in the lock file after PSR upgrades the version in pyproject.toml file.

How did you test?

I tested in my own repository where I observed the issue.

• pyproject.toml file for my repo: https://github.com/aqib-oss/sonar-qube-gh-action/blob/main/pyproject.toml
• Commit to show that the fix works: aqib-oss/sonar-qube-gh-action@ee19420

How to Verify

Create a python repo that uses uv and PSR, and follow the updated instructions for UV integration as per this PR.

PR Completion Checklist

• Reviewed & followed the Contributor Guidelines

• Changes Implemented & Validation pipeline succeeds

• Commits follow the Conventional Commits standard
  and are separated into the proper commit type and scope (recommended order: test, build, feat/fix, docs)

• Appropriate Unit tests added/updated

• N/A Appropriate End-to-End tests added/updated

• Appropriate Documentation added/updated and syntax validated for sphinx build (see Contributor Guidelines)