Repository navigation
feat(dagster): report each source's release date on its raw file - #58
Merged
Merged
Conversation
Collaborator
Author
|
@codex review |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Co-authored-by: Claude <noreply@anthropic.com>
tillywoodfield
force-pushed
the
feat/50-report-release-dates
branch
from
October 29, 2026 11:07
71b1af4 to
60212b1
Compare
tillywoodfield
marked this pull request as ready for review
October 29, 2026 11:08
Collaborator
Author
|
@codex review |
|
Codex Review: Didn't find any major issues. Keep it up! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
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.
What & why
Each raw file asset already fetches or parses its source's release date to write the
metadata.jsonsidecar, but never reported it to Dagster, so the UI couldn't show which release a download holds. The raw file assets of DAC1, DAC2A, DAC2B, CRS, WEO, IDS and Imputed Multilateral Sectors now report it asYYYY-MM-DDmetadata, under the sidecar's keys (source_release_date, orcrs_release_dateandmultisystem_release_date).Closes #50
Changes
Notes for reviewers
versionmetadata, and a date there would cost a second request a day that must not fail release detection. What the graph serves is on its provenance'simportedSourceReleaseDate.Checklist
Testing:
pre-commitchecks,dg check defsandpytest(451 passed) pass locally, rebased ondev.🤖 Generated with Claude Code