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.
Issue #, if available:
Description of changes:
test_version.py
to ensure that we don't accidentally do a release with a version that doesn't include an explicit micro / minor version. For example, we released1.2
instead of1.2.0
. While1.2
is technically valid, it causes issues with some AWS logic such as docker builds that expect an explicit micro version.version.py
file so the content aligns with the ruff formater. Previously it complained that the version file lacked a newline and should use"
instead of'
for string values. This would lead to unnecessary clutter and confusing when users would perform automated linting prior to submitting a PR.Example of the previous confusing lint message:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.