Changes required to fully and correctly release 1.4.0 #123
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.
@guardian/digital-cms
I made a couple of mistakes in the previous PR - to correctly get sbt-release to release a multiproject with differing cross scala configurations, we need to set releaseCrossBuild off (confusing! but gives control over crossbuilding to sbt, instead of sbt-release, and sbt handles it better); and include the sonatypeReleaseSettings on the root project, and sonatype won't publish without a homepage set.
Once all of that is done, the only and only correct way to run a release is
sbt clean release(and NOTsbt clean +release,sbt clean "release cross"or any other invocation which refers to crossbuilding!)