You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is not the same as the News post or Release on GitHub that contain more user friendly text and other content intended for the public.
I believe that the release notes could be generated by structured files containing the various changes labeled properly, like deprecations, notable changes, new features, updates, etc. All properly categorized. It should also contain additional sections for notes like Important information etc.
Example files:
"release_notes/1.7.0/new_features.md"
"release_notes/1.7.0/vendor_updates.md"
We could use markdown files enriched with custom makros/syntax to use constants and variables and more easily format things.
In my opinion it's better to use different files because the changelogs are huge.
Reacted by Omar, Kinimel, NightWatch404 and Wannacry-ops
Activity
Fernando-A-Rocha commentedon Jan 23, 2026
I think it's worth getting the 1.7 upcoming release Changelog coded and ready, then worry about the older ones, even the historical pages.
botder commentedon Jan 23, 2026
I would rather use Markdown-ish files for this
Fernando-A-Rocha commentedon Jan 23, 2026
You are right. Markdown files enriched with variables etc
[-]Add release notes YAML[/-][+]Add release notes pages[/+]