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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add
tlLatestVersion
,tlLatestPreReleaseVersion
to versioning plugin #333Add
tlLatestVersion
,tlLatestPreReleaseVersion
to versioning plugin #333Changes from 6 commits
bce0230
defe6b3
9572683
210a174
f23c6d2
085bdd1
c58d30b
4852218
4e2eb8e
91d747d
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, these are great descriptions! Bikeshed time, is "current release" and "current pre-release" the best terminology for these? Maybe "latest" is more appropriate? And "version" instead of "release"?
I guest that gets us to something like
tlLatestStableVersion
andtlLatestPreReleaseVersion
maybe 🤔 bit of a mouthful.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have absolutely no opinion on this but happy to change it if you like 😃
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not even a smidgeon of an opinion? 😂 I hate deciding these things. I can commit whatever I decide before I merge.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe I have a slight preference for
tlLatestStableRelease
andtlLatestPreRelease
- explicit but reasonably concise.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On the other hand,
currentRelease
isn't actually guaranteed to be a stable release:There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can I leave this with you to commit the final wording and naming? Happy to discuss ideas of course
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup, I can do that. Thanks for all your help, nice to bounce ideas! Much appreciated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah yeah sounds good, I only just saw this now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually I don't think that's correct?
tlBaseVersion
isn't used in the calculation, and this won't be the behaviour if (say)tlBaseVersion
is 1.4 but there's a stable 1.3.0 release and a 1.4.0-M1 release, right?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You are right, it's still not 100% correct.
It is, albeit indirectly.
version
is used in the calculation, andtlBaseVersion
is used to calculateversion
.You are right about this. It uses the binary series and not the
x.y
series.