For each of the following archives, find the run status in the Github archiver run. If validation tests pass, manually review the archive and publish. If no changes detected, delete the draft. If changes are detected, manually review the archive following the guidelines in step 3 of README.md, then publish the new version. Then check the box here to confirm publication status, adding a note on the status (e.g., "v1 published", "no changes detected, draft deleted"):
- [x] eia176: no changes detected, draft deleted
- [x] eia191: v12.0 published
- [x] eia757a: no changes detected, draft deleted
- [x] eia860: no changes detected, draft deleted
- [x] eia860m: v26 published
- [x] eia861: no changes detected, draft deleted
- [x] eia923: v24 published
- [x] eiaaeo: no changes detected, draft deleted
- [x] eiawater: no changes detected, draft deleted
- [x] eia_bulk_elec: updates detected (file size decreased by 5MB?). Confirmed actual .txt file size has increased, so this must be a change due to the zipping compression. v.14.0 published
- [x] epacamd_eia: no changes detected, draft deleted
- [x] ferc1: files marked as updated but all file size changes are 0 bytes - draft deleted
- [x] ferc2: files marked as updated but all file size changes are 0 bytes - draft deleted
- [x] ferc6: files marked as updated but all file size changes are 0 bytes - draft deleted
- [x] ferc60: files marked as updated but all file size changes are 0 bytes - draft deleted
- [x] ferc714: files marked as updated but all file size changes are 0 bytes - draft deleted
- [x] mshamines: v11.0 published
- [x] nrelatb: no changes detected, draft deleted
- [x] phmsagas: v11.0 published. Note that PHMSA updates the data_date in all files every month in the "_present" zipfiles, so no file should be considered an unchanging output.
Validation failures
For each run that failed because of validation test failures (seen in the GHA logs), add it to the tasklist. Download the run summary JSON by going into the "Upload run summaries" tab of the GHA run for each dataset, and follow the link. Investigate the validation failure.
If the validation failure is deemed ok after manual review (e.g., Q2 of 2024 data doubles the size of a file that only had Q1 data previously, but the new data looks as expected), go ahead and approve the archive and leave a note explaining your decision in the task list.
If the validation failure is blocking (e.g., file format incorrect, whole dataset changes size by 200%), make an issue to resolve it.
- [x] eia930: Individual file size test. The following files have absolute changes in file size >|25%|: {'eia930-2024half2.zip': 0.34590979599250254} - expected larger change in file size given that we're in H2 of the year. V10.0 published
Other failures
For each run that failed because of another reason (e.g., underlying data changes, code failures), create an issue describing the failure and take necessary steps to resolve it.
- [x] epacems: v16 published (changes detected, but no new quarter since October release) -- looks like data was released on the 2nd so we should re-run this archiver and create a new archive. See #476 for publication of v17.0
Summary of results:
See the job run logs and results here.
Review and publish archives
For each of the following archives, find the run status in the Github archiver run. If validation tests pass, manually review the archive and publish. If no changes detected, delete the draft. If changes are detected, manually review the archive following the guidelines in step 3 of
README.md, then publish the new version. Then check the box here to confirm publication status, adding a note on the status (e.g., "v1 published", "no changes detected, draft deleted"):Validation failures
For each run that failed because of validation test failures (seen in the GHA logs), add it to the tasklist. Download the run summary JSON by going into the "Upload run summaries" tab of the GHA run for each dataset, and follow the link. Investigate the validation failure.
If the validation failure is deemed ok after manual review (e.g., Q2 of 2024 data doubles the size of a file that only had Q1 data previously, but the new data looks as expected), go ahead and approve the archive and leave a note explaining your decision in the task list.
If the validation failure is blocking (e.g., file format incorrect, whole dataset changes size by 200%), make an issue to resolve it.
Other failures
For each run that failed because of another reason (e.g., underlying data changes, code failures), create an issue describing the failure and take necessary steps to resolve it.