Skip to content

docs: draft release notes for 2026-11-18.0 - #620

Merged
Adam Lastowka (Rachmanin0xFF) merged 4 commits into
mainfrom
release-notes-2026-11-18.0
Nov 18, 2026
Merged

Adam Lastowka (Rachmanin0xFF) merged 4 commits into
mainfrom
release-notes-2026-11-18.0

Conversation

@overture-pull-requester

Copy link
Copy Markdown
Contributor

Draft generated from release-candidate artifacts. Human review is required.

Signed-off-by: overture-pull-requester[bot] <280063256+overture-pull-requester[bot]@users.noreply.github.com>
@github-actions

github-actions Bot commented Nov 18, 2026 •

Copy link
Copy Markdown

🗺️ Overture Docs preview is live!

🌍 Preview site https://staging.overturemaps.org/docs/pr/620/index.html
🕐 Updated Nov 18, 2026 19:26 UTC
📝 Commit 9299cba

Note

♻️ This preview updates automatically with each push to this PR.

@github-actions

github-actions Bot commented Nov 18, 2026 •

Copy link
Copy Markdown

✅MegaLinter analysis: Success

Descriptor Linter Files Fixed Errors Max errors Warnings Elapsed time
✅ JAVASCRIPT eslint 32 0 0 20.36s
✅ MARKDOWN markdownlint 286 0 0 0.45s
✅ SQL sqlfluff 79 0 0 10.88s

See detailed reports in MegaLinter artifacts

Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining FLAVOR_SUGGESTIONS: false)

  • Documentation: Custom Flavors
  • Command: npx mega-linter-runner@10.2.0 --custom-flavor-setup --custom-flavor-linters JAVASCRIPT_ES,MARKDOWN_MARKDOWNLINT,SQL_SQLFLUFF

MegaLinter is provided by OX Security
Show us your support by starring ⭐ the repository

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These are a significant departure from the previous release notes. They are missing a lot of the markdown formatting / conventions of the previous release notes.

I don't think we should publish these as-is so I'm putting a block on this for now. We can probably just patch this (I may open a PR targeting this branch), but we should fix the prompt introduced in https://github.com/OvertureMaps/tf-data-platform/pull/6133

@Rachmanin0xFF

Adam Lastowka (Rachmanin0xFF) commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

Update: actually I think Stephen Epps (@stepps00) has his own version that he will commit onto this PR. Once that happens I'll just close my other PR without merging

Update: okay nvm he is pushing the commit to my PR. so I will merge that

@Rachmanin0xFF

Copy link
Copy Markdown
Contributor

#623 regarding the formatting failures...

@Rachmanin0xFF

Adam Lastowka (Rachmanin0xFF) commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

accessibility workflows should resolve once PR is updated with manual edits

<!-- markdownlint-disable -->
## Pull Request

Relates to #620. The automated draft in that PR doesn't follow the
format of earlier release notes. This PR rewrites the notes to match
`blog/2026-10-21-release-notes.mdx`. The longer-term fix is to update
the prompt!

Changes:

- Uses the standard overview lead, with the release and schema version
in bold.
- Restores the data and artifact paths, the `{/* truncate */}` marker,
the theme status info box, and the schema changelog and attribution
sections.
- Rewrites each theme as short bullets in past tense. Adds OSM cut-off
dates for Base, Buildings, Divisions, and Transportation.
- Uses the usual table shapes: Type, Count, and Change for Base and
Divisions. Buildings get a per-source table. Transportation gets the
dataset and count-change tables.
- Takes all numbers from the draft. Per-source building counts and
per-dataset transportation counts are October's counts plus the deltas
in the draft. The building source counts add up to the new total
exactly.

Not included, because the draft has no data for them:

- Transportation lengths (km), and the length-change table.
- The places top-level taxonomy table.
- GERS churn for Divisions.

Validation: none run. This is a content-only change.

---------

Signed-off-by: Adam Lastowka <adamlastowka@gmail.com>
Signed-off-by: Stephen Epps <stephen@overturemaps.org>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Stephen Epps <stephen@overturemaps.org>

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

The release notes describe address_levels_2 as a core field even though it is absent from schema v2.0.0, leaving the measured array element or derived coverage metric unclear.

1 open issue
What changed in this PR

Adds draft release notes for Overture’s 2026-11-18.0 data release and schema v2.0.0, generated from release-candidate artifacts for human review.

Changes:

  • Lists dataset and release-artifact locations on AWS and Azure.
  • Summarizes updates across all six themes, including feature counts, source refreshes, normalization, and GERS churn.
  • Links to the schema changelog and attribution guidance.
File Description
blog/​2026-11-18-release-notes.mdx Adds November release notes with artifact paths and theme-specific updates.

Review effort: Balanced

Comment thread blog/2026-11-18-release-notes.mdx Resolved
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
@Rachmanin0xFF
Adam Lastowka (Rachmanin0xFF) merged commit 1bc8d42 into main Nov 18, 2026
17 checks passed
@Rachmanin0xFF
Adam Lastowka (Rachmanin0xFF) deleted the release-notes-2026-11-18.0 branch November 18, 2026 19:30

This branch was previously deployed

1 inactive deployment
staging — 9299cba3 Deployed Nov 18, 2026 by Rachmanin0xFF via Cleanup #233
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.

4 participants