Add sbt-release for release automation, set 0.8.0-SNAPSHOT #49
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.
Welp, I thought I was through with project-meta contributions for awhile, but I just set up sbt-release on another project so I figured I would add it here. KeenClient-Scala has become my open source crib sheet for remembering useful SBT configuration later 😁
The release process documentation updated in the changeset is a good description of what this PR does, but in short it basically completely reduces the release process to "update changelog, run
sbt release
".Frankly, this is more frustrating than helpful until we fix the fragile build, so I'm going to try to do that next and it might be sensible to leave this unmerged until then. I just wanted to push the branch for safe keeping, and here's the PR just to let people know it's in the pipeline.