Refresh business_cycle_data.csv: 2023 → 2025 - #112
Merged
Conversation
Scheduled refresh. integrity.upstream.status is `diverged` — known to be behind the source. Run: https://github.com/QuantEcon/data-lectures/actions/runs/33464878272
There was a problem hiding this comment.
Pull request overview
Refreshes the business_cycle_data.csv dynamic snapshot from the live World Bank WDI source, updating the published bytes and associated provenance/manifest metadata so the dataset remains current and auditable within the lectures/ published tree.
Changes:
- Updated
lectures/business_cycle_data.csvto extend the series through 2025 (adds YR2024 and YR2025; revises historical values per upstream revisions). - Stamped
lectures/business_cycle_data.csv.ymlfor the refresh (retrieved,integrity.sha256,integrity.upstream.status,schema.date_range.end). - Updated provenance dump and regenerated
CATALOG.mdto reflect verified integrity status for the refreshed snapshot.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| provenance/business_cycle_metadata.md | Updated WDI series metadata dump captured during refresh. |
| lectures/business_cycle_data.csv.yml | Refreshed manifest stamps (retrieval date, integrity, date range). |
| lectures/business_cycle_data.csv | Refreshed snapshot data; includes 2024–2025 columns and upstream revisions. |
| CATALOG.md | Regenerated catalog entry (integrity now “verified”, size updated). |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
…ce dumps The pattern column's description said "YR2023 in the committed bytes" and quoted an observed range — prose the refresh stamp never touches, so the first refresh shipped it stale. Reworded to point at schema.date_range.end and validate()'s bounds instead, and the rule is now in _template.py and AGENTS.md: no prose in a dynamic snapshot's manifest may embed a fact a refresh can change. The World Bank's metadata text carries runs of blank lines up to ten deep; the builder now collapses them to one before writing both dumps, and the committed dump is normalised the same way (83 -> 43 lines, no content change), so a refresh diff shows what the source said. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This was referenced Sep 1, 2026
Closed
Closed
Closed
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
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.
Scheduled refresh of
business_cycle_data.csv(class: dynamic-snapshot,cadence: annual) bybuilders/business_cycle.pyon 2026-09-01. The builder fetched the live source, validated the result against the published contract, and wrote it; the manifest is stamped to match (retrieved,integrity.sha256,integrity.upstream: verified,schema.date_range.end) andCATALOG.mdis regenerated. Review this PR through the overlap summary below — it is the one place a revision is a decision rather than a diff.Consumers (from the manifest; AGENTS.md "Refresh, break, or schema change"):
Opened automatically by
.github/workflows/refresh-snapshots.yml. A later run of the same refresh updates this branch and PR rather than opening another.Why now: integrity.upstream.status is
diverged— known to be behind the source. Bytes changed:true. Run: https://github.com/QuantEcon/data-lectures/actions/runs/33464878272