debian-mirror-gitlab/data/deprecations/14-5-disable_strict_host_key_checking.yml

- name: "Known host required for GitLab Runner SSH executor"
  announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated.
  announcement_date: "2021-11-22"
  removal_milestone: "15.0" # the milestone when this feature is planned to be removed
  removal_date: "2022-05-22"
  breaking_change: true
  body: | # Do not modify this line, instead modify the lines below.
    In [GitLab 14.3](https://gitlab.com/gitlab-org/gitlab-runner/-/merge_requests/3074), we added a configuration setting in the GitLab Runner `config.toml` file. This setting, [`[runners.ssh.disable_strict_host_key_checking]`](https://docs.gitlab.com/runner/executors/ssh.html#security), controls whether or not to use strict host key checking with the SSH executor.

    In GitLab 15.0 and later, the default value for this configuration option will change from `true` to `false`. This means that strict host key checking will be enforced when using the GitLab Runner SSH executor.
  stage: Verify
  tiers: [Core, Premium, Ultimate]
  issue_url: https://gitlab.com/gitlab-org/gitlab-runner/-/issues/28192
  documentation_url: https://docs.gitlab.com/runner/executors/ssh.html#security
New upstream version 14.5.2+ds1 2021-12-11 22:18:48 +05:30			`- name: "Known host required for GitLab Runner SSH executor"`
			`announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated.`
			`announcement_date: "2021-11-22"`
			`removal_milestone: "15.0" # the milestone when this feature is planned to be removed`
New upstream version 14.6.3+ds1 2022-01-26 12:08:38 +05:30			`removal_date: "2022-05-22"`
New upstream version 14.7.4+ds1 2022-03-02 08:16:31 +05:30			`breaking_change: true`
New upstream version 14.5.2+ds1 2021-12-11 22:18:48 +05:30			`body: \| # Do not modify this line, instead modify the lines below.`
			In [GitLab 14.3](https://gitlab.com/gitlab-org/gitlab-runner/-/merge_requests/3074), we added a configuration setting in the GitLab Runner `config.toml` file. This setting, [`[runners.ssh.disable_strict_host_key_checking]`](https://docs.gitlab.com/runner/executors/ssh.html#security), controls whether or not to use strict host key checking with the SSH executor.

			In GitLab 15.0 and later, the default value for this configuration option will change from `true` to `false`. This means that strict host key checking will be enforced when using the GitLab Runner SSH executor.
			`stage: Verify`
			`tiers: [Core, Premium, Ultimate]`
			`issue_url: https://gitlab.com/gitlab-org/gitlab-runner/-/issues/28192`
			`documentation_url: https://docs.gitlab.com/runner/executors/ssh.html#security`