Update version for the next release (v0.27.0)

[meili-bot]

Release CHANGELOG:

⚠️ Breaking changes

• Return Task instances from task methods instead of Dict (Return task instances from task methods instead of dicts #750) @sanders41

🚀 Enhancements

• Changes utcnow() to now() with a utc time zone. (Change utcnow to now with time zone #754) @sanders41
• Adding header parameters to the client constructor (Adding a header parameters to the client constructor #771) @alallema

🐛 Bug Fixes

• Make params required in cancel_task (Make params required in cancel_task #761) @sanders41
• Don't send body for get requests (Don't send body for get requests #763) @sanders41
• Allow None for the body when updating settings (Allow None for the body when updating settings #765) @sanders41

Thanks again to @KShivendu, @alallema, @curquiza and @sanders41! 🎉

[brunoocasali]

@alallema

• Make params required in cancel_task why is it not a breaking-change?
• I don't think you should mention the internal route POST /indexes/#{@uid}/documents/fetch on the get_documents also, I was not responsible for implementing the change on this repo. Please be careful in the changelogs.

[brunoocasali]

I left the review in the comments ;)

[sanders41]

Make params required in cancel_task why is it not a breaking-change?

This could be viewed multiple ways.

1. Breaking change.
2. Bug fix. If parameters weren't sent it didn't work. This is how I discovered the issue initially. I was doing something out of the ordinary and accessed cancel_tasks directly through the TaskHandler class rather than through Client. I didn't send any params and got an error.
3. Transparent to the end user and they will see no difference. Users typically access cancel_tasks through the Client and params was already required there.

[alallema]

Make params required in cancel_task why is it not a breaking-change?

Because as @sanders41 said the user shouldn't see any differences. He shouldn't use it from TaskHandler and even if he did he'd get an error.
But I agreed that this PR should be on the Bug fixes section

I don't think you should mention the internal route POST /indexes/#{@uid}/documents/fetch on the get_documents also, I was not responsible for implementing the change on this repo. Please be careful in the changelogs.

✅

[bidoubiwa]

LGTM ✨