Repository navigation
fix: index Overture release 2026-10-21.0 - #334
Merged
Merged
Conversation
Gold check and speed, full index: run failed in build-headBase Progress: 20% (1/5 steps completed; not a time estimate).
|
This was referenced Oct 25, 2026
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.
Sets
index.sources.snapshotfrom2026-10-21to2026-10-22, so OSM, OpenAddresses and GeoNames are fetched again, andindex.sources.overtureReleaseto2026-10-21.0.2026-09-23.1→2026-10-21.0This names a new index; once released, the leader builds it while the current pods keep serving the old one. New source data can change answers like a code change can: read the gold quality and speed comments before merging, and close this pull request to decline it.