Skip to content

fix: index Overture release 2026-10-21.0 - #334

Merged
Mokto merged 1 commit into
mainfrom
source-refresh/2026-10-21.0
Oct 25, 2026
Merged

Mokto merged 1 commit into
mainfrom
source-refresh/2026-10-21.0

Conversation

@Mokto

@Mokto Mokto commented Oct 22, 2026

Copy link
Copy Markdown
Owner

Sets index.sources.snapshot from 2026-10-21 to 2026-10-22, so OSM, OpenAddresses and GeoNames are fetched again, and index.sources.overtureRelease to 2026-10-21.0.

  • Overture: 2026-09-23.1 → 2026-10-21.0

This 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.

@github-actions

github-actions Bot commented Oct 22, 2026 •

Copy link
Copy Markdown

Gold check and speed, full index: run failed in build-head

Base 08b7372 → 3d0bf4e, run gold-970c098aa0, updated 11:02:28 UTC. The run failed in step build-head after 39m29s. This is a failure of the run, not a verdict on the change: nothing here says the commit regresses. The step's own log stays in the cluster; give a maintainer the run id.

Progress: 20% (1/5 steps completed; not a time estimate).

Step Status Time Progress
build-base completed 0m00s —
build-head failed 38m48s —
eval-base pending — —
eval-head pending — —
report pending — —

@Mokto
Mokto merged commit 229ee49 into main Oct 25, 2026
16 of 18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant