Update changelog files as part of release#20
Merged
Conversation
amaksimo
approved these changes
Jan 29, 2026
amaksimo
left a comment
Contributor
There was a problem hiding this comment.
Thanks! I guess we will want to add this to tools and connectors as well :)
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.
This PR adds a workflow step to update the
CHANGELOG.mdfiles as part of the release, based on the release notes in the GitHub releases. This provides a forge-agnostic change history for the repo.This was previously set up for the Django and Tortoise ORM repos, but not for the others. I've added the workflow for all subprojects, and manually synced the
CHANGELOG.mdfiles to reflect the current state of the GitHub releases.I cloned the releases from the original repositories to provide easier access for users, and to make generating these files easier going forward. It is expected that the release notes still point to commits from the archived repo, since it will be left read-only, and those pull requests don't exist anywhere else.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.