Derive CHANGELOG.md into the published mirror #83
Labels
No labels
area:docs
area:identity
area:ops
area:plugin
area:server
channel:community
channel:direct
channel:owned
channel:press
channel:social
e2ee-constrained
gate:at-ga
gate:pre-ga
marketing
parity
relay:absent
relay:planned
relay:requested
relay:supported
risk:additive
risk:contract
risk:none
usability
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Nectenda/nectenda#83
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Part of #77. Needs the ledger (#82).
Why
The mirror is what users install from. It currently ships no changelog, and the
GitHub release notes are install instructions and a SHA-256 by design.
What to do
Generate
CHANGELOG.mdfromdocs/changelog-plugin.mdinbuild-mirror.mjs,the way
readme()already generates the README — generated, neverhand-edited, or the single-master property is lost.
Four places need it, and missing any one fails the build rather than shipping
half a change:
stage()allowlist —clean()wipes.mirrorevery run, so anything notstaged deliberately is absent;
requiredlist;readme()'s documentation links;PUBLIC_DOCS, if the source is referenced from underdocs/.Watch for
The
FORBIDDENsubstring scan, which rejectspackages/server,plan-phase,positioning.mdand more. This is why the plugin ledger is separate from theserver one. Verify with
node scripts/build-mirror.mjs --check.Remember these are published comments: the mirror is public, so nothing
staged may cite a private doc.