From 1f38729094a45c6d8393d90d24f67a0301fb1a8a Mon Sep 17 00:00:00 2001 From: Mikhail Koliada <88318005+mikhailkoliada@users.noreply.github.com> Date: Wed, 24 May 2023 20:40:00 +0200 Subject: [PATCH 1/3] README: explain -latest migration process --- README.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/README.md b/README.md index 9a1cb8a4605b..954faafc0efc 100644 --- a/README.md +++ b/README.md @@ -68,6 +68,13 @@ version for the underlying OS and This image type falls under the customer [SLA](https://github.com/customer-terms/github-online-services-sla) for actions. GA images are eventually deprecated according to our guidelines as we only support the latest 2 versions of an OS. +#### Migration Process + +GitHub Actions and Azure DevOps use the `-latest` YAML label (ex: ubuntu-latest, windows-latest, and macos-latest). These labels point towards the newest stable OS version available. + +The `-latest` migration process is gradual and happens over 1-2 months in order to allow customers to adapt their workflows to the newest OS version. During this process, any workflow using the `-latest` label, may see changes in the OS version in their workflows or pipelines. To avoid unwanted migration, users can specify a specific OS version in the yaml file (ex: macos-12, windows-2022, ubuntu-22.04). + + ## Image Releases *How to best follow along with changes* From be5a1dcd0dcba621522e95095e4d7c525352e60c Mon Sep 17 00:00:00 2001 From: Mikhail Koliada <88318005+mikhailkoliada@users.noreply.github.com> Date: Wed, 24 May 2023 20:51:42 +0200 Subject: [PATCH 2/3] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 954faafc0efc..a5c5d7c76975 100644 --- a/README.md +++ b/README.md @@ -68,7 +68,7 @@ version for the underlying OS and This image type falls under the customer [SLA](https://github.com/customer-terms/github-online-services-sla) for actions. GA images are eventually deprecated according to our guidelines as we only support the latest 2 versions of an OS. -#### Migration Process +#### Latest Migration Process GitHub Actions and Azure DevOps use the `-latest` YAML label (ex: ubuntu-latest, windows-latest, and macos-latest). These labels point towards the newest stable OS version available. From ab7214d2560407c323faf5aea524bee312cdaea5 Mon Sep 17 00:00:00 2001 From: Mikhail Koliada <88318005+mikhailkoliada@users.noreply.github.com> Date: Wed, 24 May 2023 21:01:12 +0200 Subject: [PATCH 3/3] Update README.md Co-authored-by: Sam Tran --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index a5c5d7c76975..178a42858234 100644 --- a/README.md +++ b/README.md @@ -70,7 +70,8 @@ latest 2 versions of an OS. #### Latest Migration Process -GitHub Actions and Azure DevOps use the `-latest` YAML label (ex: ubuntu-latest, windows-latest, and macos-latest). These labels point towards the newest stable OS version available. +GitHub Actions and Azure DevOps use the `-latest` YAML label (ex: `ubuntu-latest`, `windows-latest`, and `macos-latest`). These labels point towards the newest stable OS version available. + The `-latest` migration process is gradual and happens over 1-2 months in order to allow customers to adapt their workflows to the newest OS version. During this process, any workflow using the `-latest` label, may see changes in the OS version in their workflows or pipelines. To avoid unwanted migration, users can specify a specific OS version in the yaml file (ex: macos-12, windows-2022, ubuntu-22.04).