Patch Tuesday Release (1B)

[mthalman]

Patch Tuesday Release

Tasks

1. • Ensure all build agent scale sets have the appropriate number of machines allocated for a build
2. • Merge any pending PRs or commits from dev branch:
     • <placeholder link>
3. • Look up the latest NuGet CLI versions and update the nuget-info.json file with the latest patch of each major/minor version listed in the file.
4. • Wait for latest cumulative updates (LCUs) to be released (typically at 10 AM PST on Patch Tuesday).
5. • Gather list of KB numbers for the .NET Framework updates from the .NET Release team.
6. • Look up the download URL for each of the KB numbers in Microsoft Update Catalog and input them into the lcu-info.json file. If this is the first Patch Tuesday after the release of a new Windows version, you'll need to do the following extra steps for that version:
     • Add a new entry to the lcu-info.json file to associate a URL for the new Windows version and 3.5 runtime version.
     • Update the 3.5/runtime Dockerfile for the new Windows version so that the patch is applied (this can be copied from another 3.5/runtime Dockerfile in a section labeled Apply latest patch)
7. • Run the update-dependencies tool to update all the necessary files:
     • dotnet run --project .\eng\update-dependencies --datestamp-all <YYYYMMDD>
8. • Inspect generated changes for correctness
9. • Commit generated changes
10. • Create PR
11. • Get PR signoff
12. • Merge PR
13. • Wait for changes to be mirrored to internal dotnet-framework-docker repo (internal MSFT link)

14. • 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
      

15. • Queue build of dotnet-framework-docker pipeline (internal MSFT link)
16. • Confirm images have been ingested by MCR
17. • Confirm READMEs have been updated in Docker Hub for microsoft-dotnet-framework
18. • 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. • Confirm sample images have been ingested by MCR
20. • Confirm Last Modified field has been updated in Docker Hub for microsoft-dotnet-framework-samples
21. • Reply to .NET Release team with a status update email
22. • Deallocate any extra scale set build agent machines if necessary

[mthalman]

windowsservercore-1909 will not be updated today due to a delay in updating the base mcr.microsoft.com/windows/servercore:1909-amd64 image.

[mthalman]

windowsservercore-1909 has been updated today. This completes the servicing updates.