What’s the standard way to handle state locking when running terraform plan on a pull request and terraform apply on merge? I’ve got a GitHub Actions workflow set up. The plan step works fine using remote-backend with the workspace set to the PR branch. The apply step triggers on merge. It fails with Error acquiring the state lock. The lock is held by the plan run from the PR. I’ve tried adding -lock=false to the apply command but that feels risky for CXone resources. The state file is stored in S3 with DynamoDB for locking. Is there a way to release the lock from the PR run automatically or should I be using a separate backend config for the apply step?