Repository navigation
fix: strip ranges of PR numbers from release notes (RS1) - #47
Merged
Merged
Conversation
itsdoubleem
temporarily deployed
to
github-pages
November 11, 2026 11:32 — 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.
What
Release notes lose ranges of pull-request numbers — "(#47–#50)", "(#46, #51–#53)" — the way they already lost "(#31)" and "(#31 and #32)". LOGGER 1.7.0's "What's new" had two, live on /apps/logger/.
Why
They link nowhere on this site, and
cleanNotes()'s own comment says they are removed. Its pattern had no case for a range.How
tools/sync-lib.mjs: each item in the bracket may be#Nor a range#N–#M/#N-M(hyphen, en or em dash).releases/logger.md: rebuilt withnotesFile(cleanNotes(...))from the real v1.7.0 Release body. Only the two brackets went; itssource:fingerprint is what the sync computes, so the next hourly run reports both apps current and writes nothing.Testing
npm test118 pass,npm run check,npm run build; the built LOGGER page has no chore: re-shoot LOGGER's pictures on 1.7.0's clock-face START #46–#53.planApp()against both live releases (both "current") and timed 10,000-item inputs (<1 ms).Screenshots
Text only — the two "What's new" paragraphs end at "inside." and "for 9 seconds." instead of with PR numbers.
Risks and rollback
A bracket like "(#1-3)" in future notes would also be stripped. Rollback:
git push --force-with-lease origin 19627d7:main.