Upcoming changes

Instead of breaking your build on every shiny new change we want to make, we follow the following strategy:

1. Never introduce breaking API changes (unless some part of the library is broken).
2. Plan breaking API changes by deprecating the old API (marked with @Deprecated) and pointing you towards the new implementation.
3. You can safely use deprecated functionality until the next major release of the library (which is going to be 2.0).
4. Provide you with a migration plan when the next major release is available.

Any other major changes will be listed in this page.

That's all for now. Hey, check out this dude chilling over here 😗