…m(PythonVersion)` (#19288)

Avoids future regressions like #19277

---------

Co-authored-by: Claude <noreply@anthropic.com>

…19294)

## Summary

When `uv lock` is invoked with `UV_FROZEN=1` (env) or `frozen` set via
workspace configuration, the post-success warning suggested using
`--no-frozen`, which does not exist as a CLI flag. Following that hint
produces:

```
$ UV_FROZEN=1 uv lock --no-frozen
error: unexpected argument '--no-frozen' found

  tip: a similar argument exists: '--frozen'
```

Drop the bad suggestion and recommend `--check` only, matching the
sibling warning emitted when `--frozen` is passed on the CLI (introduced
in #17859).

## Old vs new warning

Before:
```
warning: The lockfile at `uv.lock` was only checked for validity, not whether it is up-to-date, because `UV_FROZEN=1` was provided; use `--no-frozen` or `--check` instead
```

After:
```
warning: The lockfile at `uv.lock` was only checked for validity, not whether it is up-to-date, because `UV_FROZEN=1` was provided; use `--check` instead
```

`--check` is defined on `LockArgs` in `crates/uv-cli/src/lib.rs` (the
public, non-hidden flag for "check if the lockfile is up-to-date") and
works regardless of whether `frozen` was set via env, configuration, or
the CLI.

## Changes

- `crates/uv/src/commands/project/lock.rs`: drop `--no-frozen` from the
env/configuration warning text.
- `crates/uv/tests/it/lock.rs`: update the `lock_frozen_warning`
snapshot to match.

## Test plan

- [x] `cargo build -p uv`
- [x] `cargo fmt --check`
- [x] `cargo clippy -p uv --all-targets -- -D warnings`
- [x] `cargo test -p uv --test it lock::lock_frozen_warning`

Closes #19290

Similar to the behavior of `uv sync --no-editable`

## Summary

And similarly for other flag pairs. I'm surprised this took so long to
get reported.

Closes #19310.

…9309)

This is a very minor doc change but fixes a bug for diligent but
unknowing new users following the guide.

The UV guide on publishing to PyPI from GHA has a screenshot showing
that users reference a "release.yml" GHA workflow file when setting up a
new Trusted Publisher in PyPI. But the guide had users create a
"publish.yml" workflow file in their GitHub repository before this. PyPI
won't grant the expected token because the workflow names don't match
exactly across PyPI and GH, so the example bombs pretty hard.

Love all your work. Thanks for your help.

<!--
Thank you for contributing to uv! To help us out with reviewing, please
consider the following:

- Does this pull request include a summary of the change? (See below.)
- Does this pull request include a descriptive title?
- Does this pull request include references to any relevant issues?
-->

## Summary

<!-- What's the purpose of the change? What does it do, and why? -->

## Test Plan

<!-- How was it tested? -->

Automated update for Python releases.

Co-authored-by: zanieb <2586601+zanieb@users.noreply.github.com>