build(deps-dev): update uv-build requirement from <0.9.0,>=0.8.0 to >=0.11.32,<0.12.0 - #4
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Conversation
Updates the requirements on [uv-build](https://github.com/astral-sh/uv) to permit the latest version. - [Release notes](https://github.com/astral-sh/uv/releases) - [Changelog](https://github.com/astral-sh/uv/blob/main/CHANGELOG.md) - [Commits](astral-sh/uv@0.8.0...0.11.32) --- updated-dependencies: - dependency-name: uv-build dependency-version: 0.11.32 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
AaronDJohnson
added a commit
that referenced
this pull request
Jul 27, 2026
Three pre-release changes that all had to land before the first tag, since
each is free now and costs a deprecation cycle afterwards.
**Block.** The unit of work is now a block: `Block`, `NoiseBlock`,
`EchoBlock`, `check_block`, `turntable.block`. That is the word blocked
Gibbs already uses for a jointly-updated group of parameters, so the
protocol name states what the sampler is doing rather than borrowing a term
("segment") that suggests a slice of the data. Several docstrings had
already drifted into saying "block" informally; they are now consistent.
**Turn.** One pass over every block is a full turn of the wheel:
`run(full_turns=...)`, `on_turn=...`, `check_block(n_turns=...)`. The Monte
Carlo literature calls this a sweep, and `run`'s docstring says so -- but a
block's own sampler *steps* many times inside a single `step()` call, and
turntable needs those two scales to be unmistakable. GLASS, the reference
LISA global fit, offers no incumbent term to defer to: its main loop is an
unnamed do/while, and its only nearby word, `cycle`, means per-module
repeats. "Iteration" is retired entirely -- it was the one word that could
plausibly mean either scale.
`examples/gb_model.py` shows the payoff: `steps_per_sweep * n_sweeps` became
`steps_per_turn * full_turns`, where before you had to know which "sweep"
was Eryn's and which was the Wheel's.
519 substitutions across 19 files; both module renames done with git mv so
history follows.
**tests/test_docs.py.** The README was the only substantial code in the repo
under no test, and it is the first thing a new user copies. Three levels:
every fenced block must parse; every call into a turntable API must use
keyword arguments that exist in the live signature (this catches exactly the
rename above, even in fragments that cannot be executed); and blocks tagged
`<!-- runnable -->` must run to completion in a fresh interpreter. The tag is
an HTML comment, so it is invisible on GitHub and stripped by PyPI's
renderer. Mutation-checked: a stale class name, a stale method name, a typo
in the quickstart, and `n_iterations=` in place of `full_turns=` are all
caught.
**Pins.** actions/checkout v5->v7, upload-artifact v4->v7,
download-artifact v4->v8 (tags verified to exist), and the uv_build floor to
>=0.11.32,<0.12.0 -- what Dependabot #1-#4 proposed, applied to both
workflows at once so ci.yml and release.yml cannot drift apart.
setup-uv stays pinned at the exact v9.0.0: there is still no floating v9 tag.
Verified beyond the suite: demo.ipynb executed cell by cell, demo.py and
toy_fit.py run (the toy fit still converges -- RMS 0.4990, sigma draw
0.4919), gb_model imports against the real LISA stack, and the sdist builds
with the new backend floor and runs all 182 tests from the unpacked tree.
100% branch coverage; ruff and mypy clean.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Owner
|
Superseded by 00fa74c, which applied this exact version bump directly. Both |
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
dependabot
Bot
deleted the
dependabot/uv/uv-build-gte-0.11.32-and-lt-0.12.0
branch
July 27, 2026 22:22
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updates the requirements on uv-build to permit the latest version.
Release notes
Sourced from uv-build's releases.
... (truncated)
Changelog
Sourced from uv-build's changelog.
... (truncated)
Commits
3010295Bump version to 0.11.32 (#20654)cb1bce0Regenerate theuv.lockTOML withuv lock --refresh(#20634)c2e07d5Remove obsolete Python upgrade preview feature (#20651)b6b2e76Reject unformatted lockfiles inuv lock --check(and--locked) (#20646)a549562Enable Ruff default lint rules across the repository (and fix all the errors)...e4e2f69Fix uv check workspace snapshots and ruff lints (#20649)241df05Add--packageand--all-packagestouv check(#20628)d332950Include best-effortenvironmentinfo by default inuv workspace metadata...b12ab98Clarify first-party trust in the threat model (#20647)1fd5716Use canonical issue references in Codex prompts (#20645)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)