Publish 1.14.3

[ashawley]

I was going to try and prepare a release of Scala.js 1.0.0-RC1 in #587 but it might be better to just release 1.14.3 with the Scala.js artifacts and with the bug-fix in #569.

Plus, a 1.0.0-RC2 version of Scala.js was released, yesterday.

[ashawley]

Drafted the release notes in #593.

[ashawley]

Going to cherry-pick the Scala.js 0.6.31 update while we're at it, see #594.

[SethTisue]

perhaps the release note should mention that #581 got fixed as well (as a consequence of the #568 fix)

[ashawley]

That's a good question. I read #581 as the same issue in #568. We can just close as a duplicate.

However, the issue with collection generators having a higher probability of failing because of the poor performing posNum or any unreliable generator will live on in #568. Erik suggested it could be improved somehow.

[ashawley]

Dear @djspiewak,

I've tagged commit 6464e98 as 1.14.3, on the 1.14.x branch, and pushed up the tag. Would you be able to deploy the branch? Just start reading the directions at the top of the shell script, release.sh. You can start at step 4. This is a relatively new script that is a WIP, so apologies in advance if it gives you trouble.

Thank you!

[djspiewak]

Script appears to be working! Release is uploading.

[djspiewak]

@ashawley Looks like the script is missing a sonatypeReleaseAll command. I'll run that manually.

Another problem I ran into is the fact that I don't actually have an sbt command, but rather an alias. The script doesn't deal with this correctly.

[djspiewak]

Oh holy crap it's not using sbt-sonatype. Wow. Okay I closed the staging repository by hand. We should probably fix that. :-)

[djspiewak]

Kk if I did things correctly, 1.14.3 should be propagating to Maven Central.

[ashawley]

Thanks, Daniel. Will keep an eye out for them.

[ashawley]

Are you seeing them, yet? I'm not seeing anything. Looking here for instance:

https://repo1.maven.org/maven2/org/scalacheck/scalacheck_2.13/1.14.3/

[djspiewak]

Just goes to show how long it's been since I released anything on Sonatype by hand… I forgot to release the repository; I just closed it. It should be syncing now. I think.

[djspiewak]

Also, appropriately enough, @xerial reacted to my post above. Much love!

[xerial]

Yeah. I'm waiting for the release :)

I guess it's a timing to automate the release on CI with sbt-sonatype. Here is some example https://github.com/wvlet/airframe/blob/master/.github/workflows/release.yml

or using sbt-ci-release will be handy https://github.com/olafurpg/sbt-ci-release

[ashawley]

Ok, looks like they got released. Thanks again for the help.

[djspiewak]

I guess it's a timing to automate the release on CI with sbt-sonatype. Here is some example https://github.com/wvlet/airframe/blob/master/.github/workflows/release.yml

Yeah it wouldn't be too difficult to do this, honestly, though I personally prefer with OSS projects to keep the actual release process local to a developer machine (since it's not clear who's GPG key and Sonatype credentials get ceded to Travis' control, but it's not an entirely comfortable feeling either way). At the very least, using sbt-sonatype rather than manually publishing to Sonatype would be a good and easy step forward.

[ashawley]

Yeah, sorry about all the difficulty. I guess I'll look in to doing it myself in the future. I've just been putting it off.

[djspiewak]

It actually wasn't all that bad. Just ran into some issues that should be reasonably easy to fix.

[xerial]

@djspiewak It makes sense. Having a script to publish from a local machine will be a good starting point.

1. Build artifacts for all cross-build combinations (e.g., Scala.js 0.6.x, 1.0.x) into a local staging folder
2. Run sonatypeBundleRelease once.