-
-
Notifications
You must be signed in to change notification settings - Fork 116
feat!: nullsafety #84
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
Conversation
c542c2f to
2966ce4
Compare
03bb0bb to
c8a4bb3
Compare
|
Is this blocked on anything? Would be lovely if a |
|
@skreborn I plan to publish a null-safety release very shortly π |
ce86e21 to
60409c5
Compare
|
Published v2.0.0-nullsafety.0 π |
|
Published v2.0.0-nullsafety.1 π |
|
Hi @felangel! If/once you're confident in the implementation here, please consider releasing this branch to stable so packages depending on this one can follow. Blog post: |
45141e9 to
8358d39
Compare
|
@munificent @filiph @kwalrath I'd love to release v2.0.0 but would like to close #107 first (see #108 for the changes I'm leaning toward making). If you have time can you take a look and weigh in on whether the change should be made to support legacy |
|
Published v2.0.0-nullsafety.4 π If all goes well, I'll release v2.0.0 this weekend. |
|
Finally merging this and publishing v2.0.0 π |
Status
READY
Breaking Changes
YES
Description
Todos