Bringing the latest changes (except the commits 2e3520c5d8fbb7ad7733d9136c5a8a668b980585 and 9fe889b80996471fae95d4dab66b5c6854394bb1, which are related to madmin-go upgrade to v3) to the v1 branch, which at the time of writing contains the code from the last working version of the provider in Terraform Registry (v1.18.0).
So, from now on, the repository will always have the main branch and the v1 branch. Whenever someone wants to bring some change to the first version of the provider, they create a pull request targeting the v1 branch.
PS: I also took the chance to re-check the state of v1.18.3 and v1.19.0, which have been released (although failing to be installed), and confirmed that both are working fine and can remain listed as releases in the repository.
Bringing the latest changes (except the commits 2e3520c5d8fbb7ad7733d9136c5a8a668b980585 and 9fe889b80996471fae95d4dab66b5c6854394bb1, which are related to madmin-go upgrade to v3) to the
v1branch, which at the time of writing contains the code from the last working version of the provider in Terraform Registry (v1.18.0).So, from now on, the repository will always have the main branch and the
v1branch. Whenever someone wants to bring some change to the first version of the provider, they create a pull request targeting thev1branch.PS: I also took the chance to re-check the state of v1.18.3 and v1.19.0, which have been released (although failing to be installed), and confirmed that both are working fine and can remain listed as releases in the repository.