We should verify that this update (#18) doesn't cause any breaking changes, and document the change in an upgrade guide.
