Release for Scala 2.13.0-RC3

[Philippus]

Tag v1.1.2#2.13.0-RC3#8 has been created, @SethTisue can you pick it up from here?

[SethTisue]

yes

publishing job is https://travis-ci.org/scala/scala-parser-combinators/builds/538949185

[Philippus]

Looks like the scala native artifacts also got published, we could release those as well?

[SethTisue]

sure, I see them on Sonatype. I'm in the middle of closing and releasing the staging repos.

[SethTisue]

sigh, something went wrong — one .asc file ended up in a staging repo all by itself, and then the whole batch failed Sonatype's checks. can you delete and then re-push the tag?

very likely it's just some race condition that will go away on retry

[Philippus]

https://travis-ci.org/scala/scala-parser-combinators/builds/538967696

[SethTisue]

shouldn't the staging repos have contained artifacts for 2.13.0-RC3 only? there were tons of 11 and 12 artifacts too. including the Scala Native artifacts. which should have tipped me off, but I'm sleepy

going to bed now, I'll look at it in the morning. (I'm in Europe early for Scala Days.)

I'm having deja vu. did this also happen last time? I can't remember if it was in this repo, or a different module repo. any clue why the tag parsing stuff isn't doing the right thing?

[SethTisue]

yeah it did happen here last time: #211 (comment)

[SethTisue]

scala-xml has the same problem, scala/scala-xml#311

[SethTisue]

oh okay, this is just how things work now, after #174. I got confused because some other modules still do it the old way

okay, I see now that it is:

# In order to build a previously released version against a new (binary incompatible) Scala release,
# a new commit that modifies (and prunes) the Scala versions in .travis.yml needs to be added on top
# of the existing tag. Then a new tag can be created for that commit, e.g., `v1.2.3#2.13.0-M5`.
# Everything after the `#` in the tag name is ignored.

[SethTisue]

• commit: 0df35a1
• tag: https://github.com/scala/scala-parser-combinators/releases/tag/v1.1.2%232.13.0-RC3
• job: https://travis-ci.org/scala/scala-parser-combinators/builds/539095436

[SethTisue]

hmm well that didn't work. it only published locally, not to Sonatype

it seems not to have gone into this if in admin/build.sh:

verPat="[0-9]+\.[0-9]+\.[0-9]+(-[A-Za-z0-9-]+)?"
tagPat="^v$verPat(#$verPat#[0-9]+)?$"

if [[ "$TRAVIS_TAG" =~ $tagPat ]]; then
  tagVer=${TRAVIS_TAG}
  tagVer=${tagVer#v}   # Remove `v` at beginning.
  tagVer=${tagVer%%#*} # Remove anything after `#`.
  publishVersion='set every version := "'$tagVer'"'

I 😐 regexes and shell scripting

[SethTisue]

It appears that contrary to the comment in admin/build.sh, the #8 at the end is required after all, note the two appearances of # in tagPat

[SethTisue]

• commit: 0df35a1
• tag: https://github.com/scala/scala-parser-combinators/releases/tag/v1.1.2%232.13.0-RC3%238
• job: https://travis-ci.org/scala/scala-parser-combinators/builds/539103324

[SethTisue]

staging repos closed, released.

now we keep an eye out at https://repo1.maven.org/maven2/org/scala-lang/modules/scala-parser-combinators_2.13.0-RC3/1.1.2/

[SethTisue]

scala/make-release-notes@725d20a

[SethTisue]

@Philippus now we both know better for next time :-)

[Philippus]

let's not change it until after 2.13.0 final is out. :)

[SethTisue]

@Philippus since you don't do Twitter (afaict), fyi https://twitter.com/SethTisue/status/1133836388615544833