Refresh official data vintages - #168
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
force-pushed
the
data/vintage-refresh
branch
from
August 12, 2026 08:01
98dcb3e to
1fd0d8c
Compare
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.
Automated ONS and Bank of England vintage refresh from
data/fetch.py.New factual release-note pages are generated from changed snapshots
on the same branch and remain subject to review before publication.
New files under
data/vintages/are new vintages — an upstreamrevision or a new observation. Nothing is edited in place, so the
diff should be additions plus the regenerated
MANIFEST.jsonandlatest/. An edit to an existing vintage file is a bug; checkthe fetcher rather than accepting it.