Skip to content

scripts/.vendored_canon_ref is pinned before history.yaml existed in the hub #670

Description

@realmarcin

`scripts/.vendored_canon_ref` is pinned to `6be694f3` (CultureMech), a commit that predates `src/culturemech/schema/history.yaml` existing in the hub (confirmed: that path 404s at this ref, 200s at later refs). MediaIngredientMech and proteintraitsmech are pinned to later refs and already vendor `history.yaml` via a `MAPPED` entry in `scripts/check_vendored_sync.sh`; this repo's own local `src/communitymech/schema/history.yaml` is currently byte-identical to the hub's current copy, so nothing is actually out of sync content-wise — only the pin (and therefore the sync check's coverage) is behind.

Companion PR (culturebotai-claw#88 propagation) intentionally left this repo's `check_vendored_sync.sh` MAPPED list without the `history.yaml` entry, since adding it before bumping the pin would make the sync check fail on a 404 rather than a real drift.

To close this: bump `scripts/.vendored_canon_ref` to a current hub commit (re-verify all vendored files still match at the new ref, since bumping can also surface unrelated drift), then add the `history.yaml` MAPPED entry to `scripts/check_vendored_sync.sh`, matching MediaIngredientMech's/proteintraitsmech's pattern.

Activity

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions