Once the new script [1] is live, we need to document the three steps needed to do an offline update of CRW 1.1 to 1.2:

[1] https://issues.jboss.org/browse/CRW-297 -> https://github.com/redhat-developer/codeready-workspaces-deprecated/blob/6.19.x/operator-installer/migrate_1.1_to_1.2.sh

a) pre-download the new images (server, operator, ubi8-minimal, sso, postgres + stacks) as in https://access.redhat.com/documentation/en-us/red_hat_codeready_workspaces/1.2/html/administration_guide/installing-codeready-workspaces-in-restricted-environments#making-codeready-workspaces-images-available-from-a-local-registry

b) push those into your internal registry as in https://access.redhat.com/documentation/en-us/red_hat_codeready_workspaces/1.2/html/administration_guide/installing-codeready-workspaces-in-restricted-environments#making-codeready-workspaces-images-available-from-a-local-registry

c) run the migrate script using override flags for the locally-sourced images from the internal custom registry

I imagine this last step will become section 6.3 of https://access.redhat.com/documentation/en-us/red_hat_codeready_workspaces/1.2/html/administration_guide/upgrading-codeready-workspaces called "Running the CodeReady Workspaces migration script in a restricted environment", or similar.