-
Notifications
You must be signed in to change notification settings - Fork 715
Generate changelogs for 3.10.3.0 #9661
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
a708fb1
to
6b52dbd
Compare
O, here is Assorted/Changelogs! So it was still running at the time of 3.10 fork off. I think it rightly requires that the changelog config is retained even when changelogs are deleted. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you.
Sanity check: it mentions #9459 that is the most crucial fix of the release AFAIR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Full disclosure: I didn't check the entries from the new changelog with the ones in the old changelogs.
I also think more backticks could be employed to highlight technical entities (e.g. extra-prog-path
). But we are unpaid volunteers, not someone paid by a backtick, so…
@Mergifyio backport master |
✅ Backports have been created
|
* Generate changelogs (cherry picked from commit 1972a17) # Conflicts: # changelog.d/base16-script-cache
* Generate changelogs Co-authored-by: Hécate Moonlight <Kleidukos@users.noreply.github.com>
Cabal 3.10.3.0 Release process: Changelogs generation.
This PR needs to be ported to
master
.Reviewers please make sure no changelog entry is already present in a previous release.