Repository navigation
Conversation
A lock that cannot be regenerated without running code the repository or one of its packages chose is now refused: the update (or lockfile maintenance) is skipped with a standing reason, never written with a stale lock. - Failure::Refused is the lockfile layer's refusal; Plan::lockfiles_failed turns it into Hold::Blocked, so it shows as a skipped update with its reason on the dashboard and in the report. The reason is the Count's own text, never tool output. - uv runs with --no-build and UV_NO_BUILD=1, and UV_PYTHON names the interpreter by version. --no-build does not stop uv building the workspace's own packages (verified with uv 0.13.6: a root or member with any dynamic metadata, a dynamic version alone included, is built), so a workspace pyproject.toml with dynamic metadata, or a member glob outside the workspace, is refused before uv runs; uv's "building is disabled" answers become refusals. - Poetry runs only under poetry_guard.py, a launcher that replaces every build entry point (pyproject_hooks' hook call, pypa/build's builder, Poetry's isolated builder and get_pep517_metadata, the installer's Chef) and plugin loading with os._exit(86), refuses to start on any other Poetry version or a missing entry point (87), and is only used at the Poetry version the canary covers; a repository pin of another Poetry is refused. - Bundler evaluates a Gemfile rendered from the Count's own Gemfile reading (patchula_manager::render_gemfile), in a scratch directory outside the checkout beside a copy of Gemfile.lock, with BUNDLE_VERSION=system and GIT_ALLOW_PROTOCOL=none; only Gemfile.lock comes back. gemspec, path/git/forge gems, any unread line and GIT, PATH or PLUGIN SOURCE lock sections are refused. - Real-tool canaries: a build backend or Ruby that writes a marker, reached directly and through another package, is refused for each tool and the marker never appears. - Bump the extract, files, config, config-files, catalog and catalog-controls state versions for the crates/manager, crates/lockfiles and crates/update edits.
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
count-patchula | 4174527 | Commit Preview URL Branch Preview URL |
Nov 16 2026, 03:15 AM |
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
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.
Stacked on #345 (base
fix/tools-sandbox). Scope: uv, Poetry and Bundler. npm, Yarn, dotnet, git transport for Node and the threat-model rewrite are onfix/no-exec-node-dotnet, which is also stacked on #345.The rule: code a repository chose never runs on the Count's machine, and package code counts as repository-chosen. What can be locked without running code is still locked. An update whose lock can't be is skipped with a standing reason on the dashboard and in the report. It is never written with a stale lock, and lockfile maintenance is skipped the same way.
The refusal path (shared)
patchula_lockfiles::Failure::Refused(String)is the error the lockfile layer returns when it refuses.Plan::lockfiles_failedturns it intoHold::Blocked(reason), the hold that already reports skipped updates, so the plan shows asSkippedwith that reason. The reason is always the Count's own text, never tool output.Runner::refusable_toolisheld_toolplus a classifier. The classifier decides whether a tool's failure means "stopped before running code", and it runs before any credentialed output is withheld.uv
Mechanism:
uv lock --no-build, plusUV_NO_BUILD=1.UV_PYTHONgives the interpreter by version, so a.python-versionthat names a path can't pick another one.Flags verified against uv 0.13.6 (
uv lock --help):--no-build Don't build source distributions [env: UV_NO_BUILD=]and-p, --python [env: UV_PYTHON=].Finding (contradicts the design note):
--no-builddoes not stop uv building the workspace's own packages. With a marker backend, uv 0.13.6 built and ran it for:dynamic = ["dependencies"]dynamic = ["version"]onlyIt also did so with
--no-build-package <root>and withUV_NO_BUILD_ISOLATION=1. Path and editable dependencies, sdists from an index, and a root with no[build-system]were refused by uv itself. Static workspace members with a[build-system]were not built.So: before uv runs, the Count refuses when any
pyproject.tomlin the workspace declares non-emptydynamic. That means the project's own file, plus every one under an ancestor that declares[tool.uv.workspace]. Amembersorexcludeglob that leaves the workspace root is also refused. Apyproject.tomlthat doesn't parse fails the run before uv reads it.uv's own "Building source distributions … is disabled", "building from source is disabled" and "has no usable wheels" answers become refusals.
Poetry
poetry lock. Poetry 2.5.1 builds throughpoetry.inspection.info.get_pep517_metadata, which usespoetry.utils.isolated_build.isolated_builder(an isolated env,build.ProjectBuilderand pyproject_hooks). Read from the installedpoetry/inspection/info.pyandpoetry/utils/isolated_build.py.python -I poetry_guard.py <version> lock --no-interaction --no-plugins ….poetryscript's shebang, including the installer's/bin/shtrampoline, and re-execs itself there with-I.os._exit(86), so Poetry can't catch it:pyproject_hooks._impl.BuildBackendHookCaller._call_hook,build._builder.ProjectBuilder.__init__,poetry.utils.isolated_build.isolated_builder,poetry.inspection.info.get_pep517_metadata,poetry.installation.chef.Chef.prepare, andPluginManager.load_plugins/add_project_plugin_path/ensure_project_plugins.main.poetry lockon a path dependency with a marker backend wrote the marker. Under the launcher it exited 86 atget_pep517_metadataand wrote no marker.--versionwithout--no-pluginsexits 86 atadd_project_plugin_path.Bundler
patchula_manager::render_gemfilerebuilds the Gemfile from the existing strict Gemfile grammar. The grammar's values now keep literal contents, so they can be written back.source,gem,group/platformsblocks andrubylines are emitted.bundle lockruns in a scratch directory under the run's driver, outside the checkout, with a copy ofGemfile.lockand anyruby file:sibling. OnlyGemfile.lockis copied back.BUNDLE_GEMFILEpoints at the rendered file,BUNDLE_APP_CONFIGat the Count's own directory, andGIT_ALLOW_PROTOCOL=none.BUNDLE_VERSION=systemwas verified in Ruby 4.0.9 / Bundler 4.0.20:bundler/settings.rbdefaultsBUNDLE_VERSIONtolockfile,bundler/self_manager.rbreturns early on"system", andman/bundle-config.1.ronndocuments it.gemspec,path:/git:/github:/other forge gems,git_source,plugin,eval_gemfile,install_if, any line the grammar does not read (Ruby code,=begin,__END__, multi-line calls), an unclosed block, aruby file:outside the Gemfile's directory, and a lock withGIT,PATHorPLUGIN SOURCEsections.Tests
--no-buildandUV_NO_BUILD/UV_PYTHONare set; uv build answers become refusals and other failures stay errorsGemfileandGemfile.lock, outside the tree) andBUNDLE_VERSION/GIT_ALLOW_PROTOCOLtest:tools):real_uv_never_builds_a_package_directly_or_transitively: a dynamic workspace package, a path dependency with a marker backend, and the same package as an sdist on a find-links index reached through another package. All three refused, no marker.real_poetry_never_builds_a_package_directly_or_transitively: the path dependency directly, and the sdist through another path package. Both refused with exit 86, no marker.real_bundler_never_evaluates_repository_ruby: a GemfileFile.writeline,gemspec, a path gem and a git gem whose gemspec writes the marker. All refused, no marker.real_uv_and_poetry_regenerate_python_locksandreal_bundler_relocks_offlinepass through the new paths.state_parity, and clippy-D warningson tools, manager, update, lockfiles and engine.Dropped / not done here
guide/lockfiles.mdare rewritten.threat-model.mdand the npm/Yarn/dotnet parts belong to the other branch.renovate/compatibility.mdanddepartures.mdare not touched, since my docs scope wasguide/lockfiles.mdandguide/managers.md. The other branch or a follow-up should note that the Count refuses these locks where Renovate runs the tools.Follow-ups
defaults.tomlneeds the guard's entry points rechecked. The canary fails closed (exit 87) if a name is missing, but a new build path would not show up as a missing name.dynamicproject withtool.uv.package = falseis refused too.