Release 1.2.0

[mandar242]

1. Updated the version number to 1.2.0
2. Ran go generate to regenerate docs
3. Ran antsibull-changelog release --version 1.2.0

[gravesm]

Could you reissue this against the stable-1 branch? We should do releases from that.

[sikha-root]

Hi! I'm not sure if this affects this PR or not, but:

• grpc 1.59.0+ (from 4m ago) needs go 1.19
• terraform-plugin-sdk 2.32.0 (from 3w ago) needs go 1.20

go.mod currently pins this provider to 1.18, and when I personally attempted to create my own release (following the README) using the already defined GHA workflows it was failing to build on the above dependencies¹². I'm not familiar with golang development but I assume this means that this project needs to be updated to use go 1.20 or 1.21?

Footnotes

1. https://github.com/317project/terraform-provider-ansible/actions/runs/7911434107/job/21595625703 ↩

2. https://github.com/317project/terraform-provider-ansible/actions/runs/7911584998/job/21595971910 ↩

[gravesm]

@sikha-root Thanks for catching this. Yes, we need to update the version in go.mod.

[sikha-root]

@gravesm Should I create a new PR based off what I tried the day before yesterday? 317pr/terraform-provider-ansible@release_1_2_0_prep...317project:terraform-provider-ansible:main (ignoring the goreleaser config changes)

[gravesm]

Sure, if you wouldn't mind creating a PR to update this, that would be great. I'd like to also update

terraform-provider-ansible/.github/workflows/integration.yml

Line 30 in e5e6448

go-version: '^1.21'

to use go-version-file: 'go.mod'. This will ensure the same version is being used to run integration tests as the version being used to build releases. This way we can catch these problems sooner.

[gravesm]

This PR appears to still be based off of the main branch, which is why it's duplicating commits that have been backported to the stable-1 branch. The commit that you've made should be rebased on the stable-1 branch.