For an engineer checking whether a pinned terraform-aws-modules version can move to compliance.tf as it is. Each compliance.tf module is built against specific major versions of its upstream module (that build is called an adapter); the tables list the upstream versions each adapter supports.
If your version is inside the range, change the source and keep your version constraint. If it is older, upgrade the upstream module first, then migrate. The Terraform and OpenTofu versions each module needs are on Compatibility with terraform-aws-modules.
If your upstream module version is below the minimum supported version, upgrade the upstream module first (staying on terraform-aws-modules/...) and verify the upgrade is clean. Then change the source to compliance.tf.
Upgrading the upstream module and migrating to compliance.tf in a single step is not recommended. Separate the two changes so you can attribute any plan diff to the right cause.
Adapters with open-ended constraints (e.g., >= 5.0.0) support all future minor and patch releases of that major version. Adapters with upper bounds (e.g., >= 10.0.0, < 11.0.0) are pinned to a single major version. When a new major version of the upstream module is released, a new adapter is added to compliance.tf.
