-
Notifications
You must be signed in to change notification settings - Fork 147
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
Update to Serde 1.0 #281
Comments
I think this is likely a breaking change, but if there's any way to conditionalize our code to cover a wide range of serde versions, maybe we can squeeze by. |
Technically it's definitely possible but I'm not going to recommend that you do it. 🤣 The way to do it would be make a |
Oy. I was thinking more along the lines of detecting the selected serde version in a build script somehow, and just emit a feature name for that. But maybe that's not possible. We need to do a semver bump. I've been procrastinating that forever. Maybe stable i128 will finally be worth advancing |
So I've got local changes for serde 1.0, and I was hoping to make a PR. It seems like the options are:
The changes are pretty trivial if we do (1), but I don't see a PR/branch with them. Would you like me to push it so it can be linked to the 0.2 milestone? If not, would you like me to take a look at one of the other options? |
We need to just do 0.2. I hate to force an upgrade on the ecosystem, but it's going to happen sometime. We'll do it in a side branch so we can batch as many breaking changes as we can at once. To that end, there's now a |
This is done on the next branch. |
Release notes for 0.9.0: https://github.com/serde-rs/serde/releases/tag/v0.9.0
Release notes for 1.0.0: https://github.com/serde-rs/serde/releases/tag/v1.0.0
The text was updated successfully, but these errors were encountered: