Skip to content

docs: match 2026-11-18 release notes to established format - #622

Merged
Adam Lastowka (Rachmanin0xFF) merged 3 commits into
release-notes-2026-11-18.0from
rachmanin0xff-fix-release-notes-2026-11-18-format
Nov 18, 2026
Merged

Adam Lastowka (Rachmanin0xFF) merged 3 commits into
release-notes-2026-11-18.0from
rachmanin0xff-fix-release-notes-2026-11-18-format

Conversation

@Rachmanin0xFF

@Rachmanin0xFF Adam Lastowka (Rachmanin0xFF) commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

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.

Restructure the generated 2026-11-18 notes to follow the layout of
previous releases: the standard overview lead, data and artifact
paths, the truncate marker, per-theme bullets with OSM cut-off dates,
and the usual count tables. Building counts by source and
transportation counts by dataset are derived from the October counts
plus the deltas in the draft. Transportation lengths and the places
taxonomy table are omitted because the draft has no data for them.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Signed-off-by: Adam Lastowka <adamlastowka@gmail.com>
@Rachmanin0xFF
Adam Lastowka (Rachmanin0xFF) force-pushed the rachmanin0xff-fix-release-notes-2026-11-18-format branch from af80eee to 1c30a9a Compare November 18, 2026 18:06
@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 15.45s
✅ MARKDOWN markdownlint 286 0 0 0.4s
✅ SQL sqlfluff 79 0 0 7.28s

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

@Rachmanin0xFF

Copy link
Copy Markdown
Contributor Author

do not merge -- waiting for a commit from stephen

@Rachmanin0xFF
Adam Lastowka (Rachmanin0xFF) marked this pull request as draft November 18, 2026 18:51
Signed-off-by: Stephen Epps <stephen@overturemaps.org>
@stepps00

Copy link
Copy Markdown
Contributor

Thanks for the updates Adam Lastowka (@Rachmanin0xFF)!

@Rachmanin0xFF
Adam Lastowka (Rachmanin0xFF) merged commit 20002cb into release-notes-2026-11-18.0 Nov 18, 2026
6 checks passed
@Rachmanin0xFF
Adam Lastowka (Rachmanin0xFF) deleted the rachmanin0xff-fix-release-notes-2026-11-18-format branch November 18, 2026 19:16

This branch was previously deployed

1 inactive deployment
staging — 3193ed14 Deployed Nov 18, 2026 by Rachmanin0xFF via Cleanup #230
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