Publishing drift: npm @jsonresume/schema is ahead of repo HEAD

[thomasdavis]

The published npm package @jsonresume/schema is at v1.2.1 while this repo's package.json HEAD is v1.1.2 — i.e. releases are being published from a source that is not this repo's default branch. This makes the canonical spec's provenance unclear for the whole ecosystem (the monorepo, resume-cli, and third-party themes all consume it).

Action: identify what was published as v1.2.1, reconcile it back into this repo's main branch, tag it, and from now on publish only from a known branch with CI. (For the record, current repo runtime deps are minimal — jsonschema@^1.4.1 — so there is no ajv/lodash/js-yaml CVE exposure on HEAD, contrary to an earlier automated note; the dev-only deps tape@4 / ajv-cli@3 are old but low-risk.)

Related: the draft job-schema should be finalized — it blocks @jsonresume/jobs adoption. Part of the org consolidation audit: jsonresume.org#275.

[thomasdavis]

Still accurate, and one of the more important items from the consolidation audit: npm @jsonresume/schema (v1.2.1) is published ahead of this repo's HEAD (v1.1.2), and that provenance gap needs reconciling as the schema moves into the jsonresume.org monorepo as packages/schema — where CI-driven publishing from a known branch is exactly the fix. Labeling for transfer; tracked under jsonresume/jsonresume.org#275.

[thomasdavis]

The publishing drift was fixed by #523 (repo reconciled to published 1.2.1). Publishing now happens from the monorepo via changesets (jsonresume.org#286), and the schema source has moved to packages/schema (jsonresume.org#283). Closing as resolved.