Configure explicit release name for changelog update task#64
Merged
Conversation
2 tasks
wcmjunior
approved these changes
Jan 30, 2026
This was referenced Jan 30, 2026
danielfrankcom
added a commit
that referenced
this pull request
Feb 2, 2026
This PR adds an explicit `version` configuration to the task which updates the hibernate dialect changelog. This should have been included in #64 but was missed. See #78 for an example of what happens without this. By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
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.
While #63 correctly updated the SQLAlchemy changelog, the PR and branch name were incorrect.
This seems to be because it pulled the latest release from GitHub metadata, rather than being told what release to use. I have added the
versionconfiguration field which should correct this.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.