Deprecating auto-forward State Tool commands

What is Auto-Forward?

A “auto-forward” occurs when the state tool encounters a project with a lock. A lock is set when a user runs state update lock for their project.

This results in the state tool using the locked version to run commands for that project.

Why is Auto-Forward being deprecated?

State Tool will support version locking through the platform runtimes in the future. The legacy implementation of “auto-forwarding” needs to be removed so we have a cleaner transition going forward.

Steps for locked project affected by the update

If your project is locked to an older version of State Tool, there are 2 options:

Follows these steps to remove locking of the state tool version (i.e. update to latest version) on your projects:

  1. Open local project’s activestate.yaml
  2. Remove the line prefixed lock:

Follow these steps to continue to use the lock version of the state tool on your project. Note that this will install an older version of the State Tool.

  1. Open local project’s activestate.yaml
  2. Identify the state tool version via the field prefixed lock:
  3. Check the current state tool version via state version
  4. If versions are not the same:
    • On Mac/Linux: Run sh <(curl -q https://platform.activestate.com/dl/cli/install.sh) -v <VERSION>
    • On Windows: Run powershell -Command "& $([scriptblock]::Create((New-Object Net.WebClient).DownloadString('https://platform.activestate.com/dl/cli/install.ps1'))) -v <VERSION>"
    • Ensure that you replace <VERSION> with the version from your activestate.yaml

Further Information