v0.10.2

Enhancements and Fixes

• The <Form> component can now take a custom component={...} prop if you want to render the form as anything other than <form> (default). It accepts both strings and components (function or class). Thanks @asvetliakov: #140
• PropType warnings for the <Errors> component should now be fixed.

Regressions

• The "pruning" of fields in the formReducer introduced in v9 has been causing some weird edge-case issues, so it has been removed. It is now recommended to use track(...) instead of referencing a field that might change/disappear over time. Docs to come soon.