Repository navigation
#138 soupsieve 4.1.1 past co-core's cap, opentelemetry-api 1.45.2; LOCAL_GENERATION 4 - #139
Merged
Merged
Conversation
….2, LOCAL_GENERATION 4 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…2; LOCAL_GENERATION 4 soupsieve 2.10 has three selector DoS advisories (GHSA-mmhr-3c5m-f64f, GHSA-6655-6qjp-jx7x, GHSA-7g44-g9rc-x53w); co-core 0.38.0's extract extra caps it <3, so [tool.uv] override-dependencies = soupsieve>=4.1,<5 replaces that requirement until the co-core bump to >=0.46.1. opentelemetry-api's floor moves to 1.45.2 (GHSA-mf5v-w3w3-f6cg). The lock moves those two alone; the co-core sources stay the co-pypi index. soupsieve is extraction stack, so LOCAL_GENERATION 3 -> 4 (processor_version 0.38.0+4). test_lock_floors.py holds both floors, the override, and a guard that fails once co-core's own requirement makes the override redundant. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…route Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…or, not only floors at it A co-core release that lifts soupsieve's cap without raising its floor (>=2.0,<5) makes the override redundant too: a constraint floor would do. The guard now reads co-core's upper bounds (< and <=, padded), with controls. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The override entry matched by prefix, and co-core's marker by substring
('extraction' would count). One _names helper for both requirement reads,
the marker matched as extra == 'extract', with controls.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…hem a new refusal Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Nov 16, 2026
This was referenced Nov 16, 2026
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.
Refs #138 (epic #84, Tier 1). Live checks remain after the merge, so this doesn't close the issue.
What
[tool.uv] override-dependencies = ["soupsieve>=4.1,<5"]. It fixes GHSA-mmhr-3c5m-f64f, GHSA-6655-6qjp-jx7x and GHSA-7g44-g9rc-x53w.extractextra caps soupsieve<3, and a constraint only narrows, so the floor has to be an override. This was the operator's decision on Lock advisories: soupsieve 4.1 (extraction child, override past co-core 0.38.0's cap; LOCAL_GENERATION +4) and opentelemetry-api 1.45.2 #138.>=4.1,<5itself.constraint-dependenciesfloor (GHSA-mf5v-w3w3-f6cg). Not extraction stack.LOCAL_GENERATION3 → 4:processor_versionbecomes0.38.0+4. soupsieve is extraction stack (spec §5).tests/test_lock_floors.py:Requires-Dist: once co-core's requirement admits soupsieve ≥ 4.1 (its floor reaches it, or its cap lifts), the guard fails and names the override to remove.tests/test_pin.py:EXTRACTION_STACKsoupsieve4.1.1,GENERATION4.Lock diff
bash scripts/co-pypi.sh uv lock --upgrade-package soupsieve --upgrade-package opentelemetry-apiresolved 64 packages and moved those two alone. The manifest recordsoverrides = [{ name = "soupsieve", specifier = ">=4.1,<5" }]. All three co-coresources are still the co-pypi index URL.Evidence
tests/processors/test_extract.py,tests/test_gen_parity_goldens.py).child containment: required (Landlock ABI 6).test_the_whole_parity_corpus_is_identical_through_the_childpasses.tests/test_child.py: 40 passed, 7 skipped (environmental: credential files this user can't read, no docker socket).integration). CI on82f35a8: 1026 passed, containmentrequired(Landlock ABI 8). The PR's audit reads 0.HtmlExtractor, thencanonical_text_fingerprint. 289 HTML files (the parity HTML, the real corpus, every HTML file over 3 KB onco-processor) × 34 selector configs, so 9,826 runs per version. The two venvs differ in soupsieve alone (2.10 / 4.1.1), with 30 s per run.div:has(p a)anddiv:has(div:has(p)): 289 files each go from a result toUnsupportedExtractionError. soupsieve 3.0's strict:has()refuses a complex or nested:has();div:has(> p)still compiles;"a >": refused on both versions, with the reason reworded (Invalid character ' ' position 1).<template>(4.0's break): selectors no longer descend into one, butHtmlExtractortakes no text from a template on either version. Probed: identical.Review
The reviewing-code pass found 4 findings, fixed as
CR 1–CR 4:A fifth (no separate red commit) is declined:
mainholds every commit green.After the merge (on #138)
scripts/deploy.sh, which also restartsprocessoronto the 11-13 glibc.processor_version0.38.0+4.mainreads 0, and Dependabot alerts 12–15 close.🤖 Generated with Claude Code