We need to improve the release process

[bschaatsbergen]

Currently releases are done when PRs are merged, we should be able to stack up a few PRs and release that under a single version.

[d-costa]

Some resources that may be useful for this:

• Release Please Action - https://github.com/google-github-actions/release-please-action
• Release Please - https://github.com/googleapis/release-please

[cblkwell]

Did we make any changes to this? With the bumping of the provider, we should probably release a new major release version -- what's the process we want to use for that?

[d-costa]

Did we make any changes to this?

Not that I'm aware of.

@bschaatsbergen how were you managing the releases? Personally I've used release-please-action in other module repositories, but it requires contributors to follow conventional commits spec...

[bschaatsbergen]

Did we make any changes to this?

Not that I'm aware of.

@bschaatsbergen how were you managing the releases? Personally I've used release-please-action in other module repositories, but it requires contributors to follow conventional commits spec...

Right now, we manually tag and cut releases, and I’m fine with adopting a convention—as long as it doesn’t introduce significant complexity that could bottleneck or stall contributions. What do you think?

[cblkwell]

Hey folks, it looks like the Terraform registry is not picking up the latest version (4.2.0); I even created an additional v4.2.0 tag which didn't fix it either. I don't appear to have access in the registry to resync, or to look at the hooks for our repository to make sure that is working. Who has access to fix this?