Fix again the strategy for determining the latest version released. #565
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
Since we want to auto publish the a test version of Django Jazzmin each time a PR is merged we have to take into account to things: * You need to know which test versions have already been released on test PyPi so between prooduction releases you don't have tag clashes. * When a production version is released to PyPi you need to start releasing test version using the new production version. Otherwise you'll stay on the initial version constantly.
|
Quite complex, but I understand the rationale, and it seems to behave as expected. |
@farridav Yeah, sadly not an elegant solution, but does the trick. Did you have a better solution or are you happy for me to merge? |
|
No let's get this moving, thanks for the work on it |
farridav
approved these changes
Apr 22, 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.
Since we want to auto-publish the a test version of Django Jazzmin each time a PR is merged, we have to take into account the following:
Before
After