fix release package naming discrepancy 13.3.0 #188
Merged
+23
−4
Conversation
This file contains 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
BenLatham
previously approved these changes
Jul 16, 2024
…upporting python 3.7
BenLatham
previously approved these changes
Jul 16, 2024
BenLatham
reviewed
Jul 16, 2024
BenLatham
reviewed
Jul 16, 2024
BenLatham
approved these changes
Jul 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Synopsis
SPP-11735
The SML releases packages for versions 13.2.0 and 13.3.0 still have the prior version number, 13.1.2, in their names.The main reason for this is that the statistical-method-library project's pyproject.toml was pointing to an earlier version 13.1.2 when later release versions were created.
Python 3.7 is no longer supported by the most recent version of the github action abatilo/actions-poetry, which is causing flake8, black, and unittest on Python 3.7 to fail.
Checklist
Description
Add a more detailed description of the pr if necessary (can reference release
notes if included).