-
Notifications
You must be signed in to change notification settings - Fork 652
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
Handle int64 numbers when writing version variables #3248
Conversation
This seems like something we should release in v5. It also feels like something that should be roll into @james-bjss' #2703 which also deals with integer parsing. Perhaps you can pick up his PR and rebase it against |
I just rebased against |
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.
True, #3028 did most of that but you've found a missed or new occurrence, which is great. I still think there's value in consistently having a TryParse()
pattern, but as it's going to fail a lot less with long
than int
, I think we can merge this and leave #2703 open as a avenue for future improvement.
Thank you @RatserX for your contribution! |
@asbjornu Is there any ETA as to when a new 5.x version is going to be released? This change would actually help us unblock a lot of our projects. |
🎉 This issue has been resolved in version 5.11.0 🎉 Your GitReleaseManager bot 📦🚀 |
Description
Long numeric values for certain version variable fields (e.g. PreReleaseNumber) cause the number parsing to fail and throw the InvalidOperationException.
WriteNumberValue supports int64 so this should be a pretty safe update.
Related Issue
Motivation and Context
How Has This Been Tested?
Screenshots (if appropriate):
Checklist: