Fill missing source_id/package_id so publish-raw covers every manifest - #149
Open
MaxGhenis wants to merge 1 commit into
Open
Fill missing source_id/package_id so publish-raw covers every manifest#149MaxGhenis wants to merge 1 commit into
MaxGhenis wants to merge 1 commit into
Conversation
Nineteen manifests predated the split of source_id (publisher) from package_id (package slug): they carried the package slug in source_id and no package_id, so chronicle publish-raw skipped them entirely. - Derive both ids from each manifest's existing content-addressed R2 keys (path convention for cms_nhe/historical_service_source, which had none), so republishing reproduces the historical keys byte-for-byte. - ssa/ssi_table_7b1_2024: correct its package path — the artifact had been uploaded under ssa-annual-statistical-supplement-2025's key. - First-time storage for three entries that publish-raw previously could not handle, including two extracted_targets label entries. All 21 artifacts are published to the PolicyEngine account's ledger-raw bucket (17 keys unchanged, 1 corrected, 3 new). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Nineteen
db/datamanifests predated the source/package id split — they carried the package slug insource_idand had nopackage_id, sochronicle publish-rawskipped them with "Manifest missing package_id/source_id" scan errors. Both ids are now filled, derived from each manifest's existing content-addressed R2 keys (path convention forcms_nhe/historical_service_source, which had no storage yet), so republishing reproduces the historical keys exactly.One deliberate correction:
ssa/ssi_table_7b1_2024's artifact had been uploaded underssa-annual-statistical-supplement-2025's package path; it now lives at its ownssa-ssi-table-7b1-2024key.Verification
Ran
publish-rawper directory over all 19 (with #148's tooling fixes): 21/21 artifacts uploaded, 0 failures, 0 scan errors to the PolicyEngine account'sledger-raw. Storage keys: 17 byte-identical to the committed ones, 1 corrected (7b1), 3 first-time entries (including twoextracted_targetslabel entries that only became publishable with #148's label-year fix). Spot round-trip (sfpd Belgian pension caseload) sha256-verified.Companion to #148, which pins the Cloudflare account and fixes the publish tooling.
🤖 Generated with Claude Code