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
IncompatibleClassChangeError with upickle 1.3.14 and 1.3.15 #351
Comments
Without bumping the major version, no tool can help avoid this kind of issues. Maybe, you can cut a new major release, and restore binary compatibility in a new micro release? |
We haven't been following strict semver - normally this kind of bin-compat breakage would bump the second number, and only "huge" source-compat breakages would bump the first. I can go push tags for uPickle and Ammonite to get numbered versions out |
Yeah, I'm aware of that. But maybe upickle should follow semver more stricktly, as it's users community grows.
That would be great! People demand using the repl from Mill with newer Scala versions, and having proper released upstream dependencies would make it much easier to create a new (binary incompatible) mill release (with it's own plugin ecosystem). |
uPickle 1.4.0 and Ammonite 2.4.0 are out; they should work together if we want to bump them both in Mill |
@lihaoyi Thank you! I'll update those in mill too. |
Here is a stacktrack which running mill with upickle 1.3.15.
How to reproduce:
build.sc
line 100 to either1.3.14
or1.3.15
mill -i dev.assembly && rm -rf ~/.mill && out/dev/assembly/dest/mill -i main.test
This is probably because mill loads plugins via
$ivy
import which are build with older versions of upickle.The text was updated successfully, but these errors were encountered: