Add release notes - #14
Merged
Merged
Conversation
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:
pyproject.tomlto ignore missing copyright notice. As per comment (and commit message) I consider this a temporary exclusion as "best practice" is to include the copyright message; but not important enough to do now...FYI I'll merge this PR as soon as it's approved but I won't rebuild with a version bump until there are actually updates of substance.
Background:
I forgot to add release notes to #13 PR. I figured it wouldn't actually be a big deal to add them and push directly to master. Turns out it was a bad idea... I put the file in the wrong place (root dir instead of
release_notes) and also needed to tweak the ruff rules to make the GH actions build succeed.