Skip to content

support re-publishing an already tagged version for a new Scala version #12

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
SethTisue opened this issue Aug 18, 2016 · 1 comment
Closed

Comments

@SethTisue
Copy link
Member

suppose you've already published version 0.3.0 of your module, but now Scala 2.12.0-M5 just came out and you want to publish again for M5 only.

@adriaanm suggests it could work as follows: you push a tag of the form v0.3.0_2.12.0-M5. we'll need to add new logic in admin/build.sh (which unfortunately each module repo has its own copy of) to recognize this as a special form of version tag and do the right thing.

we can wait and face this the first time it actually comes up.

@SethTisue
Copy link
Member Author

@lrytz done, right?

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

No branches or pull requests

1 participant