Skip to content

Conversation

@smarter
Copy link
Member

@smarter smarter commented May 23, 2021

Previously, the non-bootstrapped 3.0.1-RC1 would have had version
3.0.1-nonbootstrapped for which sbt would compute the binary version
3.0.1-nonbootstrapped since we publish a compiler compiled with that
version, this is the binary version that would have ended up on Maven.

Fixed by instead making sure the non-bootstrapped release version is
3.0.1-bin-nonbootstrapped which sbt will interpret correctly.

@smarter smarter added this to the 3.0.1-RC1 milestone May 23, 2021
@smarter smarter requested a review from adpi2 May 23, 2021 16:28
Previously, the non-bootstrapped 3.0.1-RC1 would have had version
`3.0.1-nonbootstrapped` for which sbt would compute the binary version
`3.0.1-nonbootstrapped` since we publish a compiler compiled with that
version, this is the binary version that would have ended up on Maven.

Fixed by instead making sure the non-bootstrapped release version is
`3.0.1-bin-nonbootstrapped` which sbt will interpret correctly.
@smarter smarter changed the title Use the correct scalaBinaryVersion correctly for releases Use the correct scalaBinaryVersion for releases May 23, 2021
@smarter smarter force-pushed the fix-binaryVersion-2 branch from b253559 to dc79439 Compare May 23, 2021 16:29
Copy link
Member

@adpi2 adpi2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes that works because sbt computes the binary version of 3.0.1-bin-<whatever> as being the binary version of 3.0.1 which is 3.

@adpi2 adpi2 merged commit af0de81 into scala:master May 25, 2021
@adpi2 adpi2 deleted the fix-binaryVersion-2 branch May 25, 2021 08:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants