Terraform CLI, providers and remote modules have separate versions. A constraint says which releases are acceptable; the dependency lock file records selected provider releases and integrity information. Treat an upgrade as a reviewed configuration change.
Read the relevant upgrade notes, change the intended constraint, select dependencies deliberately and inspect a fresh plan. Keep the lock file with the configuration so another operator can reproduce the selection. A local module follows the repository revision, while remote module sources need their own version selection. State written by a newer tool or provider can also affect rollback. This lab checks upgrade decisions without downloading binaries or claiming compatibility for an external provider.
A selected version must satisfy the constraint, and its resulting plan still needs review.