Automate updating of changelog and version in releasing #35
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.
In highly unexpected news, it turns out that in order to get releasing working to my satisfaction I had to throw away all of the Travis deploy infrastructure and write my own based on the hypothesis-python infrastructure.
Given that I had to do that anyway, it wasn't much extra work to get a similar release file mechanism up and running. There's enough different that this ended up being a recreation rather than a reuse, but very much the same idea: There is a
RELEASE.mdfile in the root of the repo, and this updates the associated version and date of the gemspec and then adds it to theCHANGELOG.md.Fixes #31.