May 2025 Recovery 1

[joshspicer]

• [x] Create a milestone May 2025 Recovery 1 @joshspicer
• [x] Bump the version number & run npm i to bump package-lock.json as well. Ensure there are no other package-lock.json changes. @joshspicer
• [ ] 🔖candidate issues
• [ ] Assign candidate issues to the recovery milestone team
• [ ] Review the candidate issues, and if they pass the review assign them to the recovery milestone team
• [ ] All candidate fixes are peer reviewed and pushed to main and then cherry-picked into the release branch team
• [ ] Initiate insiders build from main
• [ ] Issues are tested in the insiders team
• [ ] Build and manually release Insider from main branch for vscode.dev (if there were vscode.dev candidates)
  • [ ] Issues are tested in the insiders team
• [ ] Build stable for all platforms from release branch @joshspicer
• [ ] Issues are verified on stable build and the verified label is added @joshspicer
• [ ] Check https://github.com/Microsoft/vscode/compare/release/<x.y> to ensure no other commits have been made in the release branch @joshspicer
• [ ] The insiders build with all candidate fixes needs to be in the wild for 24 hours before recovery release, unless explicitly approved by @kieferrm
• [ ] Update the release notes and include a link to a query for the fixed issues @ntrogh
• [ ] Sanity Testing
  • [ ] Windows 64 bit owner
    • [ ] System Installer
    • [ ] User Installer
    • [ ] Archive
    • [ ] Server
    • [ ] CLI
  • [ ] Windows ARM64 owner
    • [ ] System Installer
    • [ ] User Installer
    • [ ] Archive
    • [ ] Server
    • [ ] CLI
  • [ ] macOS Intel owner
    • [ ] Archive
    • [ ] Universal Archive
    • [ ] Server
    • [ ] CLI
  • [ ] macOS ARM64 owner
    • [ ] Archive
    • [ ] Universal Archive
    • [ ] Server
    • [ ] CLI
  • [ ] Linux x64 owner
    • [ ] Archive
    • [ ] DEB
    • [ ] RPM
    • [ ] Snap
  • [ ] Linux Server and CLI owner (can be tested from any OS with Docker)
    • [ ] x64
    • [ ] ARM32
    • [ ] ARM64
    • [ ] x64 Alpine
    • [ ] ARM64 Alpine
• [ ] Publish website @rzhao271
• [ ] Publish stable build @joshspicer
• [ ] (if there were vscode.dev candidates) Trigger the vscode.dev Deploy pipeline for release/x.y for the prod deployment target. @joshspicer
  • [ ] Request approval from another team member at the necessary step to deploy the vscode.dev build. @joshspicer
• [ ] Create an official release @joshspicer
  • [ ] Create a tag (make sure you pull the release branch first): git tag <x.y.z> release/<x.y>
  • [ ] Push the tag: git push origin <x.y.z>
  • [ ] Create a GitHub release: Open the GitHub tags, and click far right ... > Create Release. Use the correct title and description from our release notes. Example
• [ ] Close the milestone on GitHub @joshspicer