chore(deps): update dependency uv to v0.4.27

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
uv (source, changelog)	==0.4.26 -> ==0.4.27

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

astral-sh/uv (uv)

v0.4.27

Compare Source

This release includes support for the [dependency-groups] table as recently standardized in PEP 735. The table allows for declaration of optional dependency groups that are not published as part of the package metadata, unlike [project.optional-dependencies]. There are new --group, --only-group, and --no-group options throughout the uv interface.

Previously, uv used a single tool.uv.dev-dependencies list for declaration of development dependencies. Now, uv supports declaring development dependencies in a standardized format and allows splitting development dependencies into multiple groups.

For compatibility, and to simplify usage for people that do not need multiple groups, uv special-cases the group named dev. The dev group is equivalent to tool.uv.dev-dependencies. The contents of tool.uv.dev-dependencies will merged into the dev group in uv's resolver. The --dev, --only-dev, and --no-dev flags remain as aliases for the corresponding --group options. Support for tool.uv.dev-dependencies remains in this release, but will display warnings in a future release.

uv syncs the dev group by default — this matches the exististing behavior for tool.uv.dev-dependencies. The default groups can be changed with the tool.uv.default-groups setting.

Thank you to Stephen Rosen who authored PEP 735.

Enhancements

• Support for PEP 735 (#​8272)
• Add support for --dry-run mode in uv lock (#​7783)
• Don't allow non-string email in authors (#​8520)
• Enforce lockfile schema versions (#​8509)

Bug fixes

• Always attach URL to network errors (#​8444)
• Fix dangling non-platform dependencies in uv tree (#​8532)
• Prefer lto over debug free-threaded managed Python builds (#​8515)

Documentation

• Add tool.uv.sources to the "Settings" reference (#​8543)
• Add reference to uv build and uv publish in the landing pages (#​8542)
• Avoid duplicate [tool.uv] header in TOML examples (#​8545)
• Document .netrc environment variable and path (#​8511)
• Fix .netrc typo in authentication docs (#​8521)
• Fix heading level of "Script support" on docs landing page (#​8544)
• Move the installation configuration docs to a separate page (#​8546)
• Update docs for --publish-url to avoid duplication. (#​8561)
• Fix typo (#​8554)
• Fix typo in description of --strict flag (#​8513)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: boundaries/shop/admin/requirements.txt

[03:41:27.984] INFO (393): Installing pip hashin@1.0.2...
[03:41:31.472] ERROR (393): Command failed with exit code 1: hashin --version
[03:41:31.473] FATAL (393): Install tool hashin failed in 3.4s.

Traceback (most recent call last):
  File "/opt/containerbase/tools/hashin/1.0.2/3.13.0/bin/hashin", line 5, in <module>
    from hashin import main
  File "/opt/containerbase/tools/hashin/1.0.2/3.13.0/lib/python3.13/site-packages/hashin.py", line 10, in <module>
    import cgi
ModuleNotFoundError: No module named 'cgi'

[sourcery-ai]

🧙 Sourcery has finished reviewing your pull request!

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

We have skipped reviewing this pull request. Here's why:

• It seems to have been created by a bot (hey, renovate[bot]!). We assume it knows what it's doing!
• We don't review packaging changes - Let us know if you'd like us to change this.

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud