Per the documentation found

CodePudding user response：

This behaviour is expected since "the step that creates or updates the environment variable does not have access to the new value, but all subsequent steps in a job will have access." (