Does PacletInfo.m allow specifying exact versions for paclet dependencies?

Goal: Create a repeatable Wolfram Language development environment where the exact versions of all paclet dependencies are fixed and guaranteed across machines.

Constraint: PacletInfo.m currently only permits specifying minimum version numbers for dependencies, and PacletInstall will resolve to the latest compatible version unless an explicit version is supplied manually. There is no built‑in lockfile or manifest analogous to package‑lock.json that records the exact resolved versions.

Uncertainty: It is unclear whether the Paclet system provides a hidden mechanism to declare exact versions, or if users must rely on external scripting to enforce pinning.

Can PacletInfo.m be extended to accept exact version constraints for dependencies? Is there a recommended workflow to emulate lockfile behavior using PacletInstall scripts?