[BUG]: 6.5.0 breaks for organization-roles API endpoint users on GHES <3.13

[isaacsanders]

Expected Behavior

The breaking change should be a breaking semver change

Actual Behavior

It’s a minor version causing a breaking change

Terraform Version

1.5.5

Affected Resource(s)

Github_organization_security_manager

Terraform Configuration Files

Steps to Reproduce

No response

Debug Output

Panic Output

Code of Conduct

• I agree to follow this project's Code of Conduct

[parente]

We spotted this regression in our Terraform plans when the 6.5.0 provider tries to read existing github_organization_security_manager resources.

Using v6.4.0 of the provider, running a plan a fine-grained access token having Organization Member read/write permission worked successfully.

Using v6.5.0, we receive an error:

Error: GET https://api.github.com/orgs/xxx/organization-roles: 403 Resource not accessible by integration []

[gk-drw]

This change makes the minimum supported GHES version for the provider to be 3.14 since it relies on https://docs.github.com/en/[email protected]/rest/orgs/organization-roles

These endpoints are used in #2533 and are returning 404 on GHES versions < 3.14

Since some of these GHES versions are still officially supported by GitHub, it would make sense to either

• revert the above pull request, or
• rework the above pull request to be able to handle both older and newer API approaches

Do you have any precedent on how to deal with this type of API bifurcation?