Add a CHANGELOG covering the last ten releases - #66
Open
ArnasDon wants to merge 1 commit into
Open
Conversation
Every release body in this repo is the same auto-generated compare link, so nothing records what changed. Seed a CHANGELOG.md from the tag history, dated from each tag, so the file has real content before the generator starts appending to it. The entries are derived from the diff between consecutive tags: tool additions, removals and redefinitions individually, everything else summarised by area, with version-string churn filtered out.
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
2 participants
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.
Seeds
CHANGELOG.mdwith the last ten releases, so the file has real history before the generator starts appending to it.Every release body in this repo is currently the same 89-character auto-generated compare link. With ~99 releases since July, nothing records what changed — including genuine capability news.
v1.48.0added two Node.js environment-variable tools andv1.50.0added a VPS firewall tool; none of that is visible anywhere today.How the entries were derived
From the diff between consecutive tags, using the generated tool list each tag carries. Tool changes are listed individually, everything else is summarised by area, and version-string churn is filtered out — otherwise every release would report the same three areas, since the version is rewritten into
package.json, the lock file and all twelve server entry points on each release.Dates come from the tags, not from when this was generated.
Depends on hostinger/public-api-generator#140
This repository is a generated mirror. The push workflow copies the downstream
.gitover a freshly generated tree and runsgit add ., which stages deletions for anything present inHEADbut absent from the generated output. Until #141 teaches the generator to writeCHANGELOG.md, the next regeneration would delete this file.Once #141 is in, the generator reads the accumulated entries from
HEADand prepends each new release, so this history persists and grows.Note on the honest entries
One section reads:
That is accurate —
v1.52.2changed 28 files, all of them version-string churn. It is worth keeping rather than hiding, since it tells a reader not to bother upgrading for that one.