GitLab protected environments need the job's environment declaration

A GitLab protected environment can limit who may deploy to a named environment and require approvals before a deployment job proceeds. Those controls depend on GitLab associating the job with that environment. The protected environments documentation warns that without the correct association, the job falls back to the regular CI/CD permission model. A production environment can be protected while a job that conceptually deploys to production is not protected at all.

The deployment job must declare an environment whose name and tier match the intended control. A group-level protection or an environment-level approval rule is only effective when the job resolves to that environment.…