Use `upload-time` rather than `upload_time` in `uv.lock` #13176

charliermarsh · 2025-04-28T13:27:37Z

Summary

In #12968, we added support for upload time to uv.lock, but stylized as upload_time. The other keys in uv.lock use kebab casing, as in common in Python formats, so this really should've been upload-time. I want to change it ASAP to minimize churn for users. Any users that already upgraded will of course experience churn in their files a second time. But if we don't change it now, we'll only increase the surface area of affected users.

So, this PR uses upload-time instead, but continues reading upload_time to make it non-breaking.

Gankra

hmm does this need a lock version bump? a previous version of uv will fail to parse upload-time.

charliermarsh · 2025-04-28T13:50:40Z

I think a previous version will just ignore it.

Gankra · 2025-04-28T13:51:47Z

Yeah, as long as the field being missing on a version that knows about the field is fine, then this is fine.

BurntSushi · 2025-04-28T13:53:47Z

Yeah versions of uv before upload_time will ignore. Versions of uv that know about upload_time but not upload-time will read upload_time but ignore upload-time.

I think the main "bad" thing that can happen is when multiple versions of uv are used to operate on the same lock file. So a newer version of uv with this change would write upload-time, but an older version would ignore that and then probably write upload_time. So then they would ping-pong. But other than that churn, I don't think anything bad can happen.

charliermarsh · 2025-04-28T14:27:00Z

Yeah confirmed old versions can read this (they just ignore it). It's only used in the PEP 751 export, so I think that's ok.

dimaqq · 2025-05-01T07:12:14Z

What you probably have not anticipated are lock files checked into version control, where one developer uses slightly older and another slightly newer version of uv and the lock files goes through a ping-pong of - and _ for a while.

Then again, this pushes folks to upgrade, that it's a win? 😆

Viicos · 2025-05-01T16:06:10Z

Maybe it's worth adding a note in the changelog whenever the lock file's version/revision is bumped, together with these kind of changes.

zanieb · 2025-05-01T16:07:53Z

@dimaqq we did consider that, see #13176 (comment)

@Viicos can you share more about what you want to see in the changelog and how it would help?

Viicos · 2025-05-01T16:12:10Z

Thanks for answering @zanieb,

in our case we have tool.uv.required-version set in our pyproject, so that all members of the team use the same uv version (or at least the same minimum version). We don't have any automated setup to update it but I regularly watch for new uv releases, and so if something like "warning: this uv version changes the lockfile output" is added in the release notes, I can easily catch it and bump our minimum version.

zanieb · 2025-05-01T17:22:11Z

Alright. Maybe we can add a dedicated "Lockfile" section — I'm not sure. We really try to avoid any churn here though, so it should be rare.

See astral-sh/uv#13176

* Migrate from mypy to pyrefly * Bump uv to avoid lock file churn * See astral-sh/uv#13176 * Add py.typed to package root to signal it supports typing

michelhe · 2025-05-05T11:46:56Z

Yeah, we also experienced the format inconsistency issues when working against a committed uv.lock file due to every developer having a different version of uv and used tool.uv.required-version to force everyone to upgrade.

This MR contains the following updates: | Package | Update | Change | |---|---|---| | [astral-sh/uv](https://github.com/astral-sh/uv) | minor | `0.6.16` -> `0.7.3` | MR created with the help of [el-capitano/tools/renovate-bot](https://gitlab.com/el-capitano/tools/renovate-bot). **Proposed changes to behavior should be submitted there as MRs.** --- ### Release Notes <details> <summary>astral-sh/uv (astral-sh/uv)</summary> ### [`v0.7.3`](https://github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#073) [Compare Source](astral-sh/uv@0.7.2...0.7.3) ##### Enhancements - Add `--dry-run` support to `uv self update` ([#9829](astral-sh/uv#9829)) - Add `--show-with` to `uv tool list` to list packages included by `--with` ([#13264](astral-sh/uv#13264)) - De-duplicate fetched index URLs ([#13205](astral-sh/uv#13205)) - Support more zip compression formats: bzip2, lzma, xz, zstd ([#13285](astral-sh/uv#13285)) - Add support for downloading GraalPy ([#13172](astral-sh/uv#13172)) - Improve error message when a virtual environment Python symlink is broken ([#12168](astral-sh/uv#12168)) - Use `fs_err` for paths in symlinking errors ([#13303](astral-sh/uv#13303)) - Minify and embed managed Python JSON at compile time ([#12967](astral-sh/uv#12967)) ##### Preview features - Build backend: Make preview default and add configuration docs ([#12804](astral-sh/uv#12804)) - Build backend: Allow escaping in globs ([#13313](astral-sh/uv#13313)) - Build backend: Make builds reproducible across operating systems ([#13171](astral-sh/uv#13171)) ##### Configuration - Add `python-downloads-json-url` option for `uv.toml` to configure custom Python installations via JSON URL ([#12974](astral-sh/uv#12974)) ##### Bug fixes - Check nested IO errors for retries ([#13260](astral-sh/uv#13260)) - Accept `musllinux_1_0` as a valid platform tag ([#13289](astral-sh/uv#13289)) - Fix discovery of pre-release managed Python versions in range requests ([#13330](astral-sh/uv#13330)) - Respect locked script preferences in `uv run --with` ([#13283](astral-sh/uv#13283)) - Retry streaming downloads on broken pipe errors ([#13281](astral-sh/uv#13281)) - Treat already-installed base environment packages as preferences in `uv run --with` ([#13284](astral-sh/uv#13284)) - Avoid enumerating sources in errors for path Python requests ([#13335](astral-sh/uv#13335)) - Avoid re-creating virtual environment with `--no-sync` ([#13287](astral-sh/uv#13287)) ##### Documentation - Remove outdated description of index strategy ([#13326](astral-sh/uv#13326)) - Update "Viewing the version" docs ([#13241](astral-sh/uv#13241)) ### [`v0.7.2`](https://github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#072) [Compare Source](astral-sh/uv@0.7.1...0.7.2) ##### Enhancements - Improve trace log for retryable errors ([#13228](astral-sh/uv#13228)) - Use "error" instead of "warning" for self-update message ([#13229](astral-sh/uv#13229)) - Error when `uv version` is used with project-specific flags but no project is found ([#13203](astral-sh/uv#13203)) ##### Bug fixes - Fix incorrect virtual environment invalidation for pre-release Python versions ([#13234](astral-sh/uv#13234)) - Fix patching of `clang` in managed Python sysconfig ([#13237](astral-sh/uv#13237)) - Respect `--project` in `uv version` ([#13230](astral-sh/uv#13230)) ### [`v0.7.1`](https://github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#071) [Compare Source](astral-sh/uv@0.7.0...0.7.1) ##### Enhancement - Add support for BLAKE2b-256 ([#13204](astral-sh/uv#13204)) ##### Bugfix - Revert fix handling of authentication when encountering redirects ([#13215](astral-sh/uv#13215)) ### [`v0.7.0`](https://github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#070) [Compare Source](astral-sh/uv@0.6.17...0.7.0) This release contains various changes that improve correctness and user experience, but could break some workflows; many changes have been marked as breaking out of an abundance of caution. We expect most users to be able to upgrade without making changes. ##### Breaking changes - **Update `uv version` to display and update project versions ([#12349](astral-sh/uv#12349 Previously, `uv version` displayed uv's version. Now, `uv version` will display or update the project's version. This interface was [heavily requested](astral-sh/uv#6298) and, after much consideration, we decided that transitioning the top-level command was the best option. Here's a brief example: ```console $ uv init example Initialized project `example` at `./example` $ cd example $ uv version example 0.1.0 $ uv version --bump major example 0.1.0 => 1.0.0 $ uv version --short 1.0.0 ``` If used outside of a project, uv will fallback to showing its own version still: ```console $ uv version warning: failed to read project: No `pyproject.toml` found in current directory or any parent directory running `uv self version` for compatibility with old `uv version` command. this fallback will be removed soon, pass `--preview` to make this an error. uv 0.7.0 (4433f41c9 2025-04-29) ``` As described in the warning, `--preview` can be used to error instead: ```console $ uv version --preview error: No `pyproject.toml` found in current directory or any parent directory ``` The previous functionality of `uv version` was moved to `uv self version`. - **Avoid fallback to subsequent indexes on authentication failure ([#12805](astral-sh/uv#12805 When using the `first-index` strategy (the default), uv will stop searching indexes for a package once it is found on a single index. Previously, uv considered a package as "missing" from an index during authentication failures, such as an HTTP 401 or HTTP 403 (normally, missing packages are represented by an HTTP 404). This behavior was motivated by unusual responses from some package indexes, but reduces the safety of uv's index strategy when authentication fails. Now, uv will consider an authentication failure as a stop-point when searching for a package across indexes. The `index.ignore-error-codes` option can be used to recover the existing behavior, e.g.: ```toml [[tool.uv.index]] name = "pytorch" url = "https://download.pytorch.org/whl/cpu" ignore-error-codes = [401, 403] ``` Since PyTorch's indexes always return a HTTP 403 for missing packages, uv special-cases indexes on the `pytorch.org` domain to ignore that error code by default. - **Require the command in `uvx <name>` to be available in the Python environment ([#11603](astral-sh/uv#11603 Previously, `uvx` would attempt to execute a command even if it was not provided by a Python package. For example, if we presume `foo` is an empty Python package which provides no command, `uvx foo` would invoke the `foo` command on the `PATH` (if present). Now, uv will error early if the `foo` executable is not provided by the requested Python package. This check is not enforced when `--from` is used, so patterns like `uvx --from foo bash -c "..."` are still valid. uv also still allows `uvx foo` where the `foo` executable is provided by a dependency of `foo` instead of `foo` itself, as this is fairly common for packages which depend on a dedicated package for their command-line interface. - **Use index URL instead of package URL for keyring credential lookups ([#12651](astral-sh/uv#12651 When determining credentials for querying a package URL, uv previously sent the full URL to the `keyring` command. However, some keyring plugins expect to receive the *index URL* (which is usually a parent of the package URL). Now, uv requests credentials for the index URL instead. This behavior matches `pip`. - **Remove `--version` from subcommands ([#13108](astral-sh/uv#13108 Previously, uv allowed the `--version` flag on arbitrary subcommands, e.g., `uv run --version`. However, the `--version` flag is useful for other operations since uv is a package manager. Consequently, we've removed the `--version` flag from subcommands — it is only available as `uv --version`. - **Omit Python 3.7 downloads from managed versions ([#13022](astral-sh/uv#13022 Python 3.7 is EOL and not formally supported by uv; however, Python 3.7 was previously available for download on a subset of platforms. - **Reject non-PEP 751 TOML files in install, compile, and export commands ([#13120](astral-sh/uv#13120), [#13119](astral-sh/uv#13119 Previously, uv treated arbitrary `.toml` files passed to commands (e.g., `uv pip install -r foo.toml` or `uv pip compile -o foo.toml`) as `requirements.txt`-formatted files. Now, uv will error instead. If using PEP 751 lockfiles, use the standardized format for custom names instead, e.g., `pylock.foo.toml`. - **Ignore arbitrary Python requests in version files ([#12909](astral-sh/uv#12909 uv allows arbitrary strings to be used for Python version requests, in which they are treated as an executable name to search for in the `PATH`. However, using this form of request in `.python-version` files is non-standard and conflicts with `pyenv-virtualenv` which writes environment names to `.python-version` files. In this release, uv will now ignore requests that are arbitrary strings when found in `.python-version` files. - **Error on unknown dependency object specifiers ([12811](astral-sh/uv#12811 The `[dependency-groups]` entries can include "object specifiers", e.g. `set-phasers-to = ...` in: ```toml [dependency-groups] foo = ["pyparsing"] bar = [{set-phasers-to = "stun"}] ``` However, the only current spec-compliant object specifier is `include-group`. Previously, uv would ignore unknown object specifiers. Now, uv will error. - **Make `--frozen` and `--no-sources` conflicting options ([#12671](astral-sh/uv#12671 Using `--no-sources` always requires a new resolution and `--frozen` will always fail when used with it. Now, this conflict is encoded in the CLI options for clarity. - **Treat empty `UV_PYTHON_INSTALL_DIR` and `UV_TOOL_DIR` as unset ([#12907](astral-sh/uv#12907), [#12905](astral-sh/uv#12905 Previously, these variables were treated as set to the current working directory when set to an empty string. Now, uv will ignore these variables when empty. This matches uv's behavior for other environment variables which configure directories. ##### Enhancements - Disallow mixing requirements across PyTorch indexes ([#13179](astral-sh/uv#13179)) - Add optional managed Python archive download cache ([#12175](astral-sh/uv#12175)) - Add `poetry-core` as a `uv init` build backend option ([#12781](astral-sh/uv#12781)) - Show tag hints when failing to find a compatible wheel in `pylock.toml` ([#13136](astral-sh/uv#13136)) - Report Python versions in `pyvenv.cfg` version mismatch ([#13027](astral-sh/uv#13027)) ##### Bug fixes - Avoid erroring on omitted wheel-only packages in `pylock.toml` ([#13132](astral-sh/uv#13132)) - Fix display name for `uvx --version` ([#13109](astral-sh/uv#13109)) - Restore handling of authentication when encountering redirects ([#13050](astral-sh/uv#13050)) - Respect build options (`--no-binary` et al) in `pylock.toml` ([#13134](astral-sh/uv#13134)) - Use `upload-time` rather than `upload_time` in `uv.lock` ([#13176](astral-sh/uv#13176)) ##### Documentation - Changed `fish` completions append `>>` to overwrite `>` ([#13130](astral-sh/uv#13130)) - Add `pylock.toml` mentions where relevant ([#13115](astral-sh/uv#13115)) - Add ROCm example to the PyTorch guide ([#13200](astral-sh/uv#13200)) - Upgrade PyTorch guide to CUDA 12.8 and PyTorch 2.7 ([#13199](astral-sh/uv#13199)) ### [`v0.6.17`](https://github.com/astral-sh/uv/releases/tag/0.6.17) [Compare Source](astral-sh/uv@0.6.16...0.6.17) #### Release Notes ##### Preview features - Add PyTorch v2.7.0 to GPU backend ([#13072](astral-sh/uv#13072)) ##### Bug fixes - Avoid panic for invalid Python versions ([#13077](astral-sh/uv#13077)) - Block scripts from overwriting `python` ([#13051](astral-sh/uv#13051)) - Check distribution names to handle invalid redirects ([#12917](astral-sh/uv#12917)) - Check for mismatched package and distribution names on resolver thread ([#13088](astral-sh/uv#13088)) - Fix panic with invalid last character in PEP 508 name ([#13105](astral-sh/uv#13105)) - Reject `requires-python` even if not listed on the index page ([#13086](astral-sh/uv#13086)) #### Install uv 0.6.17 ##### Install prebuilt binaries via shell script ```sh curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.6.17/uv-installer.sh | sh ``` ##### Install prebuilt binaries via powershell script ```sh powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.6.17/uv-installer.ps1 | iex" ``` #### Download uv 0.6.17 | File | Platform | Checksum | |--------|----------|----------| | [uv-aarch64-apple-darwin.tar.gz](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-aarch64-apple-darwin.tar.gz) | Apple Silicon macOS | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-aarch64-apple-darwin.tar.gz.sha256) | | [uv-x86\_64-apple-darwin.tar.gz](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-x86\_64-apple-darwin.tar.gz) | Intel macOS | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-x86\_64-apple-darwin.tar.gz.sha256) | | [uv-aarch64-pc-windows-msvc.zip](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-aarch64-pc-windows-msvc.zip) | ARM64 Windows | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-aarch64-pc-windows-msvc.zip.sha256) | | [uv-i686-pc-windows-msvc.zip](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-i686-pc-windows-msvc.zip) | x86 Windows | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-i686-pc-windows-msvc.zip.sha256) | | [uv-x86\_64-pc-windows-msvc.zip](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-x86\_64-pc-windows-msvc.zip) | x64 Windows | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-x86\_64-pc-windows-msvc.zip.sha256) | | [uv-aarch64-unknown-linux-gnu.tar.gz](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-aarch64-unknown-linux-gnu.tar.gz) | ARM64 Linux | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-aarch64-unknown-linux-gnu.tar.gz.sha256) | | [uv-i686-unknown-linux-gnu.tar.gz](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-i686-unknown-linux-gnu.tar.gz) | x86 Linux | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-i686-unknown-linux-gnu.tar.gz.sha256) | | [uv-powerpc64-unknown-linux-gnu.tar.gz](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-powerpc64-unknown-linux-gnu.tar.gz) | PPC64 Linux | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-powerpc64-unknown-linux-gnu.tar.gz.sha256) | | [uv-powerpc64le-unknown-linux-gnu.tar.gz](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-powerpc64le-unknown-linux-gnu.tar.gz) | PPC64LE Linux | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-powerpc64le-unknown-linux-gnu.tar.gz.sha256) | | [uv-s390x-unknown-linux-gnu.tar.gz](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-s390x-unknown-linux-gnu.tar.gz) | S390x Linux | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-s390x-unknown-linux-gnu.tar.gz.sha256) | | [uv-x86\_64-unknown-linux-gnu.tar.gz](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-x86\_64-unknown-linux-gnu.tar.gz) | x64 Linux | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-x86\_64-unknown-linux-gnu.tar.gz.sha256) | | [uv-armv7-unknown-linux-gnueabihf.tar.gz](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-armv7-unknown-linux-gnueabihf.tar.gz) | ARMv7 Linux | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-armv7-unknown-linux-gnueabihf.tar.gz.sha256) | | [uv-aarch64-unknown-linux-musl.tar.gz](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-aarch64-unknown-linux-musl.tar.gz) | ARM64 MUSL Linux | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-aarch64-unknown-linux-musl.tar.gz.sha256) | | [uv-i686-unknown-linux-musl.tar.gz](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-i686-unknown-linux-musl.tar.gz) | x86 MUSL Linux | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-i686-unknown-linux-musl.tar.gz.sha256) | | [uv-x86\_64-unknown-linux-musl.tar.gz](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-x86\_64-unknown-linux-musl.tar.gz) | x64 MUSL Linux | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-x86\_64-unknown-linux-musl.tar.gz.sha256) | | [uv-arm-unknown-linux-musleabihf.tar.gz](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-arm-unknown-linux-musleabihf.tar.gz) | ARMv6 MUSL Linux (Hardfloat) | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-arm-unknown-linux-musleabihf.tar.gz.sha256) | | [uv-armv7-unknown-linux-musleabihf.tar.gz](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-armv7-unknown-linux-musleabihf.tar.gz) | ARMv7 MUSL Linux | [checksum](https://github.com/astral-sh/uv/releases/download/0.6.17/uv-armv7-unknown-linux-musleabihf.tar.gz.sha256) | </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this MR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this MR, check this box --- This MR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).

This was due to an inconsistency between uv 0.6.15 and 0.7.0. Either version can understand a lock file written by the other, but 0.7 will automatically rewrite it with 'upload-time' whenever it makes a change, resulting in a huge diff that makes it very hard to see what actually changed. astral-sh/uv#13176

This was due to an inconsistency between uv 0.6.15 and 0.7.0. Either version can understand a lock file written by the other, but 0.7+ will automatically rewrite it with 'upload-time' whenever it makes a change, resulting in a huge diff that makes it very hard to see what actually changed. astral-sh/uv#13176

charliermarsh force-pushed the charlie/kebab branch 2 times, most recently from dfc2600 to 21f5ff0 Compare April 28, 2025 13:37

charliermarsh requested review from BurntSushi, Gankra and zanieb April 28, 2025 13:37

charliermarsh marked this pull request as ready for review April 28, 2025 13:37

Gankra approved these changes Apr 28, 2025

View reviewed changes

BurntSushi approved these changes Apr 28, 2025

View reviewed changes

Use kebab

055e221

charliermarsh force-pushed the charlie/kebab branch from 21f5ff0 to 055e221 Compare April 28, 2025 14:29

charliermarsh merged commit bb0158d into main Apr 28, 2025
82 of 85 checks passed

charliermarsh deleted the charlie/kebab branch April 28, 2025 15:01

BrewTestBot mentioned this pull request Apr 29, 2025

uv 0.7.0 Homebrew/homebrew-core#221925

Merged

ulgens mentioned this pull request Apr 30, 2025

Upgrade uv to the latest 0.7.1 dependabot/dependabot-core#12129

Merged

5 tasks

dimaqq mentioned this pull request May 1, 2025

lock file change upload-time --> upload_time #13247

Closed

twrightsman added a commit to BfArM-MVH/grz-tools that referenced this pull request May 2, 2025

build: bump uv version to avoid lock churn

92776b1

See astral-sh/uv#13176

twrightsman added a commit to BfArM-MVH/grz-tools that referenced this pull request May 2, 2025

build: bump uv version to avoid lock churn

bf2635f

See astral-sh/uv#13176

twrightsman mentioned this pull request May 5, 2025

test: improve type checks and declare typing support BfArM-MVH/grz-pydantic-models#13

Merged

neutrinoceros mentioned this pull request May 5, 2025

Lock file maintenance neutrinoceros/rlic#149

Merged

1 task

vdusek mentioned this pull request May 16, 2025

feat: Add redirected actor logs apify/apify-client-python#403

Merged

prashantgupta24 mentioned this pull request May 16, 2025

✨ add doc lint fix vllm-project/vllm-spyre#164

Merged

takana-v mentioned this pull request May 20, 2025

feat(e2k): kanalizerに移行 VOICEVOX/voicevox_engine#1694

Merged

chiwanpark mentioned this pull request May 31, 2025

chore: update uv.lock due to uv version upgrade chiwanpark/tinylm#6

Merged

zzstoatzz mentioned this pull request Jun 9, 2025

Replaced deprecated logic in SPCS worker PrefectHQ/prefect#18105

Merged

4 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Use `upload-time` rather than `upload_time` in `uv.lock` #13176

Use `upload-time` rather than `upload_time` in `uv.lock` #13176

Uh oh!

charliermarsh commented Apr 28, 2025

Uh oh!

Gankra left a comment

Uh oh!

charliermarsh commented Apr 28, 2025

Uh oh!

Gankra commented Apr 28, 2025

Uh oh!

BurntSushi commented Apr 28, 2025

Uh oh!

charliermarsh commented Apr 28, 2025

Uh oh!

Uh oh!

dimaqq commented May 1, 2025 •

edited

Loading

Uh oh!

Viicos commented May 1, 2025

Uh oh!

zanieb commented May 1, 2025

Uh oh!

Viicos commented May 1, 2025

Uh oh!

zanieb commented May 1, 2025

Uh oh!

michelhe commented May 5, 2025

Uh oh!

Uh oh!

Use upload-time rather than upload_time in uv.lock #13176

Use upload-time rather than upload_time in uv.lock #13176

Uh oh!

Conversation

charliermarsh commented Apr 28, 2025

Summary

Uh oh!

Gankra left a comment

Choose a reason for hiding this comment

Uh oh!

charliermarsh commented Apr 28, 2025

Uh oh!

Gankra commented Apr 28, 2025

Uh oh!

BurntSushi commented Apr 28, 2025

Uh oh!

charliermarsh commented Apr 28, 2025

Uh oh!

Uh oh!

dimaqq commented May 1, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Viicos commented May 1, 2025

Uh oh!

zanieb commented May 1, 2025

Uh oh!

Viicos commented May 1, 2025

Uh oh!

zanieb commented May 1, 2025

Uh oh!

michelhe commented May 5, 2025

Uh oh!

Uh oh!

Use `upload-time` rather than `upload_time` in `uv.lock` #13176

Use `upload-time` rather than `upload_time` in `uv.lock` #13176

dimaqq commented May 1, 2025 •

edited

Loading