Task releaseEarly requests Bintray credentials when Sonatype is selected

[JanBessai]

See #34 :
With version 2.1.1+4-9d76569a and sbt +releaseEarly I get:

java.lang.RuntimeException: Missing bintray credentials. Either create a credentials file with the bintrayChangeCredentials task, set the BINTRAY_USER and BINTRAY_PASS environment variables or pass bintray.user and bintray.pass properties to sbt.

even though my build.sbt specifies to publish using sonatype.

The full travis log is also available.

PR #37 provides a potential mitigation.

[JanBessai]

Fixed by accepted PR #37

[jvican]

@JanBessai Could you update the README with the latest versions, as well as the docs? Would be highly appreciated, I've just invited you to join the repo

[JanBessai]

@jvican I never got travis working for the new travis.com domain people are supposed to use now - their credential upload has a security bug which I've reported and never got a reply. Additionally, the OpenSSL version in their default boxes is horribly out of date (March 2016). At its present state, this makes me hesitant to recommend Travis to anybody in a tutorial.

I instead switched to Github actions and I'll now sowly migrate all of my other projects.
The actions workflow for the one I have finished required some hacks to find if we are on head of master, SONATYPE_USERNAME and SONA_USER as well as SONATYPE_PASSWORD and SONA_PASS each had to be set simultaneously (which might be a bug in releaseEarly), and I had to override gpg to get it to accept its password via stdin using the --pinentry-mode loopback flag.

What is you opinion on this: Do you think the README should describe Github actions despite all issues I mentioned above? Or should they be fixed first instead of guiding people to use hacks?

[jvican]

What is you opinion on this: Do you think the README should describe Github actions despite all issues I mentioned above? Or should they be fixed first instead of guiding people to use hacks?

If we can fix these bugs and address some of these "hacks" that would be great! I'm all in with moving to GitHub actions, I think they are the feature and every project will eventually use them.