[CHORE] Remove overture_releases.yaml - #552
Open
John McCall (lowlydba) wants to merge 3 commits into
Open
Conversation
Closes #551. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Signed-off-by: John McCall <john@overturemaps.org>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Signed-off-by: John McCall <john@overturemaps.org>
There was a problem hiding this comment.
Pull request overview
This PR removes the legacy overture_releases.yaml release-discovery artifact now that STAC is the source of truth, and adjusts automation/docs to stop generating/publishing it. It also freezes releases.json as a static, deprecated artifact while continuing to generate latest.ddb from STAC.
Changes:
- Deleted
overture_releases.yamland removed its publication from the GitHub Pages build workflow. - Updated
utils/fetch_releases_from_stac.pyto stop writingreleases.json(only generateslatest.ddbnow). - Added a frozen root
releases.jsonand updated README deprecation messaging accordingly.
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
utils/fetch_releases_from_stac.py |
Stops regenerating releases.json; continues generating latest.ddb from STAC. |
releases.json |
Adds a frozen, deprecated static releases.json at repo root. |
README.md |
Updates release discovery/deprecation note to reflect removal/freeze. |
overture_releases.yaml |
Removes deprecated YAML release listing from the repo. |
.github/workflows/build-manifests.yml |
Drops YAML publish step; now publishes root releases.json and latest.ddb. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Francisco Jiménez (jjcfrancisco)
approved these changes
Aug 11, 2026
Francisco Jiménez (jjcfrancisco)
left a comment
Francisco Jiménez (jjcfrancisco)
left a comment
Member
There was a problem hiding this comment.
Lgtm
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.
Closes #551.
overture_releases.yamlno longer serves a purpose now thatutils/fetch_releases_from_stac.pygenerates release metadata from the STAC catalog. This deletes the file, drops thecp overture_releases.yaml publish/step frombuild-manifests.yml, and updates the README deprecation note to reflect the removal.releases.jsonis frozen too: it's now a static file at the repo root, copied verbatim from its last deployed contents (labs.overturemaps.org/data/releases.json) with a_commentfield marking it deprecated and pointing at the STAC catalog.fetch_releases_from_stac.pyno longer writes it, onlylatest.ddb.What changed, in plain terms
overture_releases.yamlreleases.jsonlatest.ddboverture_releases.yaml/releases.json