Allow building an existing tag against a new Scala version #59
Conversation
|
Review by @SethTisue. Once this is merged, I'll cherry-pick it on top of |
|
@lrytz I won't have time tonight or tomorrow to really think about or properly review this... I think you should just go ahead. maybe comment the script a little better to help our community module maintainers understand what this is about? and/or add a comment to scala/sbt-scala-module#16? @benhutchison to expand a bit, the context for this is that 2.13.0-M1 is out now and we want to publish all the modules for it, but the existing release script doesn't have a concept of "publish existing module version for new Scala version", all it knows how to do is publish a new module version. so this addresses that by letting us push a special tag to republish an existing module version for a specified Scala version. |
|
OK, thanks Seth. I'll add more documentation and give it a go. |
lrytz
force-pushed
the
tag-with-scala-version
branch
2 times, most recently
from
9dbc775 to
18c1db0
Compare
For tags of the form `v1.2.3-suffix#2.13.0-M1`, the build script releases version `1.2.3-suffix` using Scala version `2.13.0-M1`. This allows building an existing tag against a new Scala version.
lrytz
force-pushed
the
tag-with-scala-version
branch
from
18c1db0 to
dc658b5
Compare
|
For testing, I created two tags:
It worked as expected, I checked the staging repos on sonatype. |
|
I realize i have to add one more dimension (#N) for the java major version, see scala/sbt-scala-module#18 |
For tags of the form
v1.2.3-suffix#2.13.0-M1, the build scriptreleases version
1.2.3-suffixusing Scala version2.13.0-M1.This allows building an existing tag against a new Scala version.