You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Bump co-core 0.38.0 → ≥ 0.46.1 and drop the soupsieve override (#138) #140
#138 (PR #139) took soupsieve 4.1.1 for three DoS advisories. It got there with [tool.uv] override-dependencies = ["soupsieve>=4.1,<5"], because co-core 0.38.0's extract extra caps soupsieve <3. An override replaces co-core's requirement outright, so it should be temporary. co-core v0.46.1 and later require soupsieve>=4.1,<5 themselves (CannObserv/cannobserv#667), which makes the override redundant. The latest tag is v0.48.2 (read 2026-11-16).
What
Bump co-core (and co-core-aio, co-core-sync) from 0.38.0 to a release ≥ 0.46.1, following DEPENDENCIES.md § Bumping co-core. Specific to this bump:
Remove the soupsieve override.tests/test_lock_floors.py::test_co_core_still_needs_the_override fails once co-core's own requirement admits soupsieve 4.1. Remove the override-dependencies entry and the OVERRIDDEN row, and update the floor tests. Because co-core's own floor is then 4.1, no constraint floor is needed.
Goldens and corpus: regenerate the parity goldens from co-core directly, and paste every moved digest into the bump note. The real corpus passes unchanged, or the note names what moved.
processor_version becomes <new co-core>+<LOCAL_GENERATION>. Watcher gets notice before deploy (on watcher#394 or its successor). It needs coordination instead only if the contract changes.
Parked in epic #84 (operator, 2026-11-16). Nothing forces it today: Dependabot shows 0 open alerts, and the audit on main reads 0. tests/test_lock_floors.py::test_co_core_still_needs_the_override makes any co-core bump remove the override.
Re-entry trigger, whichever comes first:
a new advisory in a package that co-core 0.38.0 caps;
soupsieve 4.1.2 on PyPI (more quadratic-time fixes);
A reason to aim this bump at v0.51.0 or later: cannobserv v0.51.0 (tagged and published 2026-11-20) maps the source-spec key include_description (CannObserv/cannobserv#559).
What changed.extraction_config_from_spec now maps extraction.include_description: true on full_page specs. On an RSS or Atom body, XmlExtractor then appends each item's description as a fifth tab field.
Why the order matters. Archiver's schema will accept the key (Source specs: expose XmlExtractConfig's include_description archiver#353) only after Processor runs v0.51.0 or later. A Processor on an older co-core drops the key without error: it extracts the four-field line and records a fingerprint that doesn't match the spec. That's why the order is cannobserv → Processor → Archiver.
New refusals surface as extraction_error (UnsupportedExtractionError is a ValueError):
true on a non-full_page spec;
true on an HTML, PDF, CSV/Excel or JSON body;
true on non-feed XML, an RSS 1.0 rdf:RDF root included.
No existing spec changes. Without the key, or with false, every config is byte-identical, so the key itself moves no parity golden. The catch-up from 0.38.0 still crosses the extract changes in between (CannObserv/cannobserv#557, CannObserv/cannobserv#570, CannObserv/cannobserv#354 and others), as the body above says.
Target. v0.51.0 satisfies this issue's ≥ 0.46.1, so one bump can cover both the soupsieve override and this.
Activity
gregoryfoster commentedon Nov 16, 2026
Parked in epic #84 (operator, 2026-11-16). Nothing forces it today: Dependabot shows 0 open alerts, and the audit on
mainreads 0.tests/test_lock_floors.py::test_co_core_still_needs_the_overridemakes any co-core bump remove the override.Re-entry trigger, whichever comes first:
At the bump, also adopt CannObserv/cannobserv#530's
store_reporting(released in v0.41.0), as the epic's Waits table records.gregoryfoster commentedon Nov 21, 2026
A reason to aim this bump at v0.51.0 or later: cannobserv v0.51.0 (tagged and published 2026-11-20) maps the source-spec key
include_description(CannObserv/cannobserv#559).extraction_config_from_specnow mapsextraction.include_description: trueonfull_pagespecs. On an RSS or Atom body,XmlExtractorthen appends each item's description as a fifth tab field.extraction_error(UnsupportedExtractionErroris aValueError):trueon a non-full_pagespec;trueon an HTML, PDF, CSV/Excel or JSON body;trueon non-feed XML, an RSS 1.0rdf:RDFroot included.false, every config is byte-identical, so the key itself moves no parity golden. The catch-up from 0.38.0 still crosses the extract changes in between (CannObserv/cannobserv#557, CannObserv/cannobserv#570, CannObserv/cannobserv#354 and others), as the body above says.≥ 0.46.1, so one bump can cover both the soupsieve override and this.