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

Use consistent version numbering #9

Merged
merged 1 commit into from Feb 22, 2017

Conversation

Projects
None yet
3 participants
@ambs
Contributor

ambs commented Feb 4, 2017

This is a CPAN Pull Request Challenge pull request.

This PR makes all modules share the same version number, as suggested by CPANTS.

@coveralls

This comment has been minimized.

Show comment
Hide comment
@coveralls

coveralls Feb 4, 2017

Coverage Status

Coverage remained the same at 90.152% when pulling 06427ad on ambs:PRC/reversion into caa79d9 on DrHyde:master.

Coverage Status

Coverage remained the same at 90.152% when pulling 06427ad on ambs:PRC/reversion into caa79d9 on DrHyde:master.

@DrHyde DrHyde merged commit 35c7ec8 into DrHyde:master Feb 22, 2017

2 checks passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
coverage/coveralls Coverage remained the same at 90.152%
Details
@DrHyde

This comment has been minimized.

Show comment
Hide comment
@DrHyde

DrHyde Feb 22, 2017

Owner

Thanks, applied, although it's quite possible that they'll get out of sync again in the future mostly cos my habit is to just update the version number in files that I'm editing. I'd happily accept a further patch that tests that they're in sync :-)

Owner

DrHyde commented Feb 22, 2017

Thanks, applied, although it's quite possible that they'll get out of sync again in the future mostly cos my habit is to just update the version number in files that I'm editing. I'd happily accept a further patch that tests that they're in sync :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment