diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-09-08 18:09:24 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-09-08 18:09:24 +0300 |
commit | 132b8909c81349a88317a00b94c1de97e2db4b74 (patch) | |
tree | 1f3bd9b2cb79ebceaa31694eb9f2df2333502937 /data | |
parent | 73e7987ee3249d40057ee5f57b2aeb876f8f9c77 (diff) |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'data')
-rw-r--r-- | data/deprecations/15-9-JWT-OIDC.yml | 6 | ||||
-rw-r--r-- | data/deprecations/16-0-Vault-integration.yml | 4 |
2 files changed, 5 insertions, 5 deletions
diff --git a/data/deprecations/15-9-JWT-OIDC.yml b/data/deprecations/15-9-JWT-OIDC.yml index 48e1b862032..5ed2b27e539 100644 --- a/data/deprecations/15-9-JWT-OIDC.yml +++ b/data/deprecations/15-9-JWT-OIDC.yml @@ -1,7 +1,7 @@ --- - title: "Old versions of JSON web tokens are deprecated" announcement_milestone: "15.9" # (required) The milestone when this feature was first announced as deprecated. - removal_milestone: "16.5" # (required) The milestone when this feature is planned to be removed + removal_milestone: "17.0" # (required) The milestone when this feature is planned to be removed breaking_change: true # (required) Change to false if this is not a breaking change. reporter: dhershkovitch # (required) GitLab username of the person reporting the change stage: Verify # (required) String value of the stage that the feature was created in. e.g., Growth @@ -32,9 +32,9 @@ - CI/CD jobs that use the `id_tokens` keyword can use ID tokens with `secrets:vault`, and will not have any `CI_JOB_JWT*` tokens available. - Jobs that do not use the `id_tokens` keyword will continue to have the `CI_JOB_JWT*` - tokens available until GitLab 16.5. + tokens available until GitLab 17.0. - In GitLab 16.5, the deprecated tokens will be completely removed and will no longer + In GitLab 17.0, the deprecated tokens will be completely removed and will no longer be available in CI/CD jobs. # diff --git a/data/deprecations/16-0-Vault-integration.yml b/data/deprecations/16-0-Vault-integration.yml index 987ac2bed3c..422852a5477 100644 --- a/data/deprecations/16-0-Vault-integration.yml +++ b/data/deprecations/16-0-Vault-integration.yml @@ -19,7 +19,7 @@ # - title: "HashiCorp Vault integration will no longer use CI_JOB_JWT by default" announcement_milestone: "15.9" # (required) The milestone when this feature was first announced as deprecated. - removal_milestone: "16.5" # (required) The milestone when this feature is planned to be removed + removal_milestone: "17.0" # (required) The milestone when this feature is planned to be removed breaking_change: true # (required) Change to false if this is not a breaking change. reporter: dhershkovitch # (required) GitLab username of the person reporting the change stage: Verify # (required) String value of the stage that the feature was created in. e.g., Growth @@ -40,7 +40,7 @@ - CI/CD jobs that use the `id_tokens` keyword can use ID tokens with `secrets:vault`, and will not have any `CI_JOB_JWT*` tokens available. - Jobs that do not use the `id_tokens` keyword will continue to have the `CI_JOB_JWT*` - tokens available until GitLab 16.5. + tokens available until GitLab 17.0. # If an End of Support period applies, the announcement should be shared with GitLab Support # in the `#spt_managers` channel in Slack, and mention `@gitlab-com/support` in this MR. # |