Repository navigation
What's new follows a release's notes when they are edited - #44
Merged
Merged
Conversation
The sync took a release's notes once, when the version arrived. Now each releases/<slug>.md records a fingerprint of the GitHub text it came from (source:), and an hourly run that finds the release's notes changed writes the file again. A hand edit to the file lasts until the release text changes; notes edited down to nothing keep what the page has.
…7-S1, R7-S2) - A same-version rewrite takes the version from apps/<slug>.md, not the tag: v1.0 and 1.0.0 compare equal, and the build checks the former. - Notes with a phrase npm run check refuses stop that app's new version, or leave an edit untaken with a warning, instead of failing every candidate. - releases/README says a hand edit needs its source: line and that refused edits are only in the run log (R7-S3, R7-N1).
Notes edited down to nothing, or to a phrase the site refuses, were one ::warning:: line an hour in a green run. planApp now says so (notes.held), and the sync raises an Issue per app through the listing Issue path, closing it once the page shows the release's notes again.
itsdoubleem
temporarily deployed
to
github-pages
November 9, 2026 06:41 — with
GitHub Actions
Inactive
itsdoubleem
temporarily deployed
to
github-pages
November 9, 2026 06:43 — 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
Editing a release's notes on GitHub now updates the app page's "What's new" within the hour. Before, the site copied the notes once, when the version arrived, and kept them.
Why
The owner edited LOGGER 1.5.0's description and the site didn't follow it.
How
releases/<slug>.mdrecordssource:, a fingerprint of the GitHub text it was written from. When the release's text no longer matches, the hourly sync writes the file again, through the usual testedsync/candidate→mainpath.npm run checkrefuses, the page keeps what it has, and one Issue (notes-<slug>) stays open until the notes are fixed. A new version with such notes is stopped for that app only. A rewrite uses the version inapps/<slug>.md, not the tag.Testing
npm test: 117 pass (7 new).npm run buildandnpm run checkpass.--issues; the file was reverted.Screenshots
None. After the merge, the hourly sync will update LOGGER's "What's new" with the owner's current 1.5.0 description. The owner chose to publish it as written.
Risks and rollback
git revertthe four commits.