bumping up next version to 0.17 (fixes RT#92865) #22
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
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.
Hi again :)
Perl Fuse has historically used single-dotted version numbers (0.1, 0.2, ..., 0.15, 0.16) for its distributions, but the latest version changed to double-dotted semantic versioning (0.16.1). This change confused CPAN as it translates 0.16.1 to 0.016001, which is lower than 0.160000 (0.16), and because of that 0.16 is still marked as latest.
This is a simple pull request that bumps $VERSION to 0.17, assuming you want to keep single-dotted versions. This will fix https://rt.cpan.org/Public/Bug/Display.html?id=92865 and allow people to seamlessly install the latest version of Fuse through CPAN.
Hope it helps!