Repository navigation
docs: match 2026-11-18 release notes to established format - #622
Merged
Adam Lastowka (Rachmanin0xFF) merged 3 commits intoNov 18, 2026
Conversation
Adam Lastowka (Rachmanin0xFF)
requested a review
from a team
as a code owner
November 18, 2026 18:05
John McCall (lowlydba)
approved these changes
Nov 18, 2026
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>
Adam Lastowka (Rachmanin0xFF)
force-pushed
the
rachmanin0xff-fix-release-notes-2026-11-18-format
branch
from
November 18, 2026 18:06
af80eee to
1c30a9a
Compare
✅MegaLinter analysis: Success
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
|
…ase-notes-2026-11-18-format
Contributor
Author
|
do not merge -- waiting for a commit from stephen |
Adam Lastowka (Rachmanin0xFF)
marked this pull request as draft
November 18, 2026 18:51
Signed-off-by: Stephen Epps <stephen@overturemaps.org>
Contributor
|
Thanks for the updates Adam Lastowka (@Rachmanin0xFF)! |
Stephen Epps (stepps00)
requested a review
from Jeff Underwood (jeffdefacto)
November 18, 2026 19:04
Stephen Epps (stepps00)
marked this pull request as ready for review
November 18, 2026 19:04
Jeff Underwood (jeffdefacto)
approved these changes
Nov 18, 2026
Adam Lastowka (Rachmanin0xFF)
merged commit Nov 18, 2026
20002cb
into
release-notes-2026-11-18.0
6 checks passed
Adam Lastowka (Rachmanin0xFF)
deleted the
rachmanin0xff-fix-release-notes-2026-11-18-format
branch
November 18, 2026 19:16
Adam Lastowka (Rachmanin0xFF)
temporarily deployed
to
staging
November 18, 2026 19:16 — with
GitHub Actions
Inactive
This branch was previously deployed
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.

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:
{/* truncate */}marker, the theme status info box, and the schema changelog and attribution sections.Not included, because the draft has no data for them:
Validation: none run. This is a content-only change.