Release version 1.0.4

[SethTisue]

The immediate motivation is to make sure that (now that #193 has landed) we have publishing set up correctly on GitHub Actions

But there is also one user-visible change, which is that thanks to the sbt-scala-module upgrade we now declare a semantic versioning policy

this time only:

• add secrets to GitHub settings, as per sbt-ci-release readme instructions

usual release steps:

• merge PRs
• choose version number
  • v1.0.4
• tag the release
  • https://github.com/scala/scala-parallel-collections/releases/tag/v1.0.4
• wait for release build
  • https://github.com/scala/scala-parallel-collections/actions/runs/1284678250
• artifacts on Maven Central
  • https://repo1.maven.org/maven2/org/scala-lang/modules/scala-parallel-collections_3/1.0.4/
  • (not a complete list)
• readme updates? build.sbt updates?
  • fee6294

[SethTisue]

hmm

2021-09-28 23:21:50.772Z error [SonatypeClient] [close] Failed  - (SonatypeClient.scala:182)
2021-09-28 23:21:50.772Z error [SonatypeClient] Activity name:close, started:2021-09-28T23:21:26.219Z  - (SonatypeClient.scala:456)
2021-09-28 23:21:50.773Z error [SonatypeClient]     Failed: signature-staging, failureMessage:No public key: Key with id: (2838a2c567f74226) was not able to be located on <a href="http://pgp.mit.edu:11371">http://pgp.mit.edu:11371</a>. Upload your public key and try the operation again.  - (SonatypeClient.scala:375)
2021-09-28 23:21:50.774Z error [Sonatype] [STAGE_FAILURE] Failed to close the repository.  - (Sonatype.scala:425)

[SethTisue]

it worked the second time after I re-submitted the key, maybe I fat-fingered it the first time 🤷