Automate releases with sbt-ci-release #17
Merged
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
except `developers` because sbt requires a URL even though it's optional in the pom
dwickern
force-pushed
the
publish
branch
2 times, most recently
from
3794ee3
to
e691c3f
Compare
dwickern
force-pushed
the
publish
branch
2 times, most recently
from
998072b
to
da6c95d
Compare
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.
https://github.com/sbt/sbt-ci-release
We need to build Play 2.9 with JDK 11 and older releases with JDK 8, otherwise we would force all users to upgrade JDK. This is a bit of a headache for me to publish manually, so I'm automating it.