Skip to content

Bump co-core 0.38.0 → ≥ 0.46.1 and drop the soupsieve override (#138) #140

Open

Description

@gregoryfoster

Why

#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.
  • A catch-up across releases (0.38.0 → 0.4x): read each CHANGELOG's Downstream lines for the extract, bus and blob-store surfaces, and diff those packages between the tags, as Take co-core's XML and feed extractors in step with Watcher, and re-run parity with a feed fixture #29 did. Releases 0.39–0.46 include breaking changes elsewhere in co-core, so check them against what Processor imports.
  • 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.
  • Strict :has() is already live from 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, so it isn't new at this bump. Watcher was told on watcher#394.

Not in scope

  • soupsieve 4.1.2 (unreleased as of 2026-11-16) can ride this bump if co-core's lock or our re-lock picks it up. Otherwise it is its own stack move.

Done when

  • co-core is pinned == at the chosen release (≥ 0.46.1), and the lock has no overrides entry for soupsieve.
  • The goldens are regenerated, with the bump note listing moved digests. The real corpus passes. CI is green by job.
  • Watcher has notice, the deploy is done, and live processor_version reads the new value.

Refs #138, #84.

Activity

  1. gregoryfoster commented on Nov 16, 2026

    @gregoryfoster
    MemberAuthor

    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:

    At the bump, also adopt CannObserv/cannobserv#530's store_reporting (released in v0.41.0), as the epic's Waits table records.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    dependenciesPull requests that update a dependency file

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions