Task · BBC-0001

Bump CATALOG_SCHEMA_VERSION to 0.2.0 once the fleet runs a binary that accepts it

Status
In Progress
Labels
blocked-external, catalog-schema
Updated
2026-08-14

Description

The schema_version this repo publishes is deployment-coupled, not a free choice. Bumblebee’s directory loader requires every catalog in the –exposure-catalog directory to declare the SAME schema_version; a mismatch exits 2 before the scan starts, emitting no packages, no findings and no scan_summary. Detection is off while every alert stays green, because there is nothing left to alert on.

State today: the deployed release accepts 0.1.0 only and hard-rejects 0.2.0. Bumblebee main accepts both and its bundled threat_intel catalogs are already bumped, but no release carries it. So this repo publishes 0.1.0.

BLOCKED ON TWO FACTS OUTSIDE THIS REPO, IN ORDER:

  1. a Bumblebee release supporting 0.2.0 exists;
  2. the deployment’s pinned BUMBLEBEE_VERSION has been raised to it AND HAS ROLLED OUT.

Only then does this task become actionable. Bumping ahead of the rollout silently drops every catalog in this repo from every scan. Do not do it to ‘stay current’.

The change itself is small and touches three surfaces that must move together: CATALOG_SCHEMA_VERSION in .github/workflows/osv-catalog.yml and .github/workflows/extra-catalogs.yml, BUMBLEBEE_RELEASE in both (the validation target must be the release that accepts the new schema), and the docstring in ci/validate.py plus the table in README.md, which both state the current coupling as fact.

Acceptance Criteria

Definition of Done

References

View the source file on GitHub