Skip to content
Snippets Groups Projects

Update token deprecation

Merged James Heimbuck requested to merge master-patch-adf7 into master
All threads resolved!
1 file
+ 4
2
Compare changes
  • Side-by-side
  • Inline
@@ -112,11 +112,11 @@ When using the native HashiCorp Vault integration, CI/CD jobs will fail when no
</div>
<div class="deprecation removal-160 breaking-change">
<div class="deprecation removal-170 breaking-change">
### Default CI/CD job token (`CI_JOB_TOKEN`) scope changed
Planned removal: GitLab <span class="removal-milestone">16.0</span> <span class="removal-date"></span>
Planned removal: GitLab <span class="removal-milestone">76.0</span> <span class="removal-date"></span>
WARNING:
This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/).
@@ -128,6 +128,8 @@ In 15.9 we extended this functionality with a better solution, an "inbound" scop
In 16.0, this inbound scope limit will be the only option available for all projects, and the outbound limit setting will be removed. To prepare for this change, you can enable the ["inbound" CI/CD job token limit](https://docs.gitlab.com/ee/ci/jobs/ci_job_token.html#configure-the-job-token-scope-limit) feature now, and list any projects that need to access your project.
In 17.0, all projects will have the inbound scope limit enabled.
</div>
<div class="deprecation removal-1511 breaking-change">
Loading