Toni Müller

How is your experience with it @aksh1618 ? Do you have any troubles? Do you think we need better support for autoformat or is it working as expected?

Maybe we can play with this option, as it is related: https://github.com/stevearc/conform.nvim/pull/488

Ok, my plan is the following: 1. Tag the current state of the main branch as `v0.0.0` 2. Try to collect all needed breaking changes (for now) in a feature...

I pushed tag `v0.0.1` Thanks for your input.

Awesome. Tag `v1.0.0` is pushed. I'm still not very keen on writing release notes, but maybe we find something for that in the future. For now I'm happy it's over...

Ahh, maybe you could enable the `Releases` feature for this repo? So that the users can see the created tags: https://docs.github.com/en/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags EDIT: I realized, we see the tags already. If...

I thought about it a little more. We could use Googles ReleasePlease Github Action to create Releases. Example: https://github.com/Robitx/gp.nvim/blob/main/.github/workflows/release-please.yml But it also may not be needed.

Ahh, just to keep in mind. This is a breaking change, as it changes the current config, so we need to communicate that.

Hi @skoch13 , to bring this forward, you would have to do the following: 1. Change the target of this PR to https://github.com/okuuva/auto-save.nvim/tree/first-breaking-changes 2. Add logic to the [handle_deprecations](https://github.com/okuuva/auto-save.nvim/blob/1747cf21c6df4806cceaa1f5f6c0ae837162f284/lua/auto-save/config.lua#L28) method,...

@skoch13 It's fine, I'll merge your commit in https://github.com/okuuva/auto-save.nvim/pull/58