Skip to content

Package project locks in PEP 517 builds - #22595

Draft
konstin wants to merge 2 commits into
konsti/build-packaged-lockfrom
konsti/build-packaged-lock-pep517
Draft

konstin wants to merge 2 commits into
konsti/build-packaged-lockfrom
konsti/build-packaged-lock-pep517

Conversation

@konstin

@konstin konstin commented Oct 15, 2026

Copy link
Copy Markdown
Member

uv build can package a project's runtime lock when building through PEP 517, extending #22067 beyond the bundled uv_build fast path. Automatic export also works when uv_build runs through PEP 517; other backends require tool.uv.export-lock = true or UV_EXPORT_LOCK=true.

The frontend adds the lock to the completed source distribution or wheel and updates the wheel's RECORD. A wheel rebuilt from a source distribution carries its packaged lock after uv verifies the source distribution's metadata and lock.

@konstin
konstin deployed to automations October 15, 2026 12:28 — with GitHub Actions Active
@konstin
konstin force-pushed the konsti/build-packaged-lock-pep517 branch from 8f45fa7 to c079a06 Compare October 15, 2026 12:42
@konstin
konstin force-pushed the konsti/build-packaged-lock branch from 56d90c9 to 0526f5f Compare October 15, 2026 12:42
@konstin
konstin deployed to automations October 15, 2026 12:43 — with GitHub Actions Active
@codspeed

codspeed Bot commented Oct 15, 2026 •

Copy link
Copy Markdown

Merging this PR will degrade performance by 10.19%

⚠️ 8 benchmarks spent significant time in system calls

System calls cannot be consistently instrumented, so they are not included in the measure, which understates the real cost. Please switch to the Walltime instrument to accurately measure system calls.

Measurement and system calls

❌ 1 regressed benchmark
✅ 68 untouched benchmarks
⏩ 54 skipped benchmarks1

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

Mode Benchmark BASE HEAD Efficiency
❌ ⚠️ Simulation discover_workspace_from_all_members_with_excludes 148.5 ms 165.4 ms -10.19%

Tip

Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.


Comparing konsti/build-packaged-lock-pep517 (b75dd9a) with konsti/build-packaged-lock (0526f5f)2

Open in CodSpeed

Footnotes

  1. 54 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

  2. No successful run was found on konsti/build-packaged-lock (b73eb4e) during the generation of this report, so 1ec0824 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

@konstin
konstin force-pushed the konsti/build-packaged-lock branch from 0526f5f to d40a366 Compare October 15, 2026 13:35
@konstin
konstin force-pushed the konsti/build-packaged-lock-pep517 branch from c079a06 to 3ef6087 Compare October 15, 2026 13:35
@konstin
konstin force-pushed the konsti/build-packaged-lock-pep517 branch from 3ef6087 to b75dd9a Compare October 15, 2026 13:36
@konstin
konstin force-pushed the konsti/build-packaged-lock branch from d40a366 to b73eb4e Compare October 15, 2026 13:36
@konstin
konstin deployed to automations October 15, 2026 13:42 — with GitHub Actions Active

This branch was successfully deployed

1 active deployment
automations — b75dd9ac Deployed Oct 15, 2026 by konstin via review / security review #51146
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant