Patch Tuesday Release - 2B

[mthalman]

Patch Tuesday Release

Tasks

1. • [x] Ensure all build agent scale sets have the appropriate number of machines allocated for a build
2. • [x] Merge any pending PRs or commits from dev branch:
     • [x] https://github.com/microsoft/dotnet-framework-docker/pull/878
3. • [x] Look up the latest recommended NuGet CLI version and set the nuget|version variable to that version in the manifest.versions.json file.
4. • [x] Wait for latest cumulative updates (LCUs) to be released (typically at 10 AM PST on Patch Tuesday).
5. • [x] Gather list of KB numbers for the .NET Framework updates from the .NET Release team.
6. • [x] Look up the download URL for each of the KB numbers in Microsoft Update Catalog and input them into the manifest.versions.json file. If this is the first Patch Tuesday after the release of a new Windows version, you'll need to do the following for that version:
     • [ ] Add a new entry to the manifest.versions.json file to associate a URL for the new Windows version.
7. • [x] Update the datestamp variables in the manifest.json file. The datestamp for a particular image's tag should only be updated if any of the following conditions are met:
     • The version of .NET Framework in the image has been serviced since the last release. (This includes servicing directly within the Dockerfile or from the base Windows image, see https://github.com/microsoft/dotnet-framework-docker/issues/783.)
     • Changes within the .NET Framework Dockerfile have caused the content of the image to be materially changed since the last release (e.g. new version of VS Build Tools, new version of NuGet CLI).
8. • [x] Run the update-dependencies tool to update all the necessary files:
     • [x] dotnet run --project .\eng\update-dependencies
9. • [x] Inspect generated changes for correctness
10. • [x] Commit generated changes
11. • [x] Create PR
12. • [x] Get PR signoff
13. • [x] Merge PR
14. • [x] Wait for changes to be mirrored to internal dotnet-framework-docker repo (internal MSFT link)

15. • [x] Run the Get-BaseImageStatus.ps1 script and wait until the Windows images have been updated as part of the Windows Patch Tuesday release process. This script will display when the dependent Windows images were last updated. Wait until all the images show that they have been recently updated. "Recently updated" amounts to be having been updated within the past week or so; images from a month ago should be considered to be the old version.

      ./eng/common/Get-BaseImageStatus.ps1 -Continuous

16. • [x] Queue build of dotnet-framework-docker pipeline (internal MSFT link)
17. • [x] Confirm READMEs have been updated in Docker Hub for microsoft-dotnet-framework
18. • [x] Confirm build for dotnet-docker-framework-samples (internal MSFT link) was queued. This will be queued automatically by dotnet-docker-tools-check-base-image-updates when it detects that the product images have been updated (detection runs on a schedule). Alternatively, you can manually queue the samples build.
19. • [x] Confirm Last Modified field has been updated in Docker Hub for microsoft-dotnet-framework-samples
20. • [ ] Reply to .NET Release team with a status update email
21. • [x] Deallocate any extra scale set build agent machines if necessary

[mthalman]

Holding on closing this until https://github.com/microsoft/dotnet-framework-docker/issues/889 is resolved.