VS Code Browser Release 1.71

[mustard-mh]

Endgame: microsoft/vscode#158841

Expected release date: 08/31

DRI: @jeanp413 @mustard-mh
Plan:

• Create corresponding release branches for main and gp-code/main
  • Create release branch release/1.71
    • Execute the rebase from upstream: ./scripts/sync-with-upstream.sh upstream/release/1.71 release/1.71
  • Create release branch gp-code/release/1.71
    • Execute the rebase from upstream: ./scripts/sync-with-upstream.sh upstream/release/1.71 gp-code/release/1.71
    • Turn off all experimental feature flags in gitpod-web
      • Ports view
• Switch nightly jobs in https://github.com/gitpod-io/openvscode-releases and Gitpod Code-Nightly GitHub actions to point to the release branches
  • insiders-gp.yml
  • insiders.yml
  • code-nightly.yaml
• Create and merge PR in Gitpod repo to generate stable image for VS Code
  • Use the template from https://gist.github.com/filiptronicek/be19dcab639a1cdf08089cc762377a41
  • Smoke test version 1.71 in VS Code Insiders
• Create and merge PR in Gitpod repo updating VS Code stable image tags to image generated in previous step
  • constants.go
• Deploy VS Code Insiders as stable
• Release OpenVSCode Server
• Port fixes from release/1.71 to main if any
• Switch nightly jobs in https://github.com/gitpod-io/openvscode-releases and Gitpod Code-Nightly GitHub actions to point back to main and gp-code/main branch
• Monitor for recovery releases and provide corresponding release in Gitpod and OpenVSCode if necessary

[mustard-mh]

Preparing a new release to make js-debug gets tunnels proposal API, and align extensionEnabledApiProposals fields with MS 🙏

Updates:

• Triggered Code Nightly job with gp-code/main branch updated
• Triggered openvscode-server Release job

Deployed 🎉

[loujaybee]

We have some reports of issues with programmatic opening of web views:

@mustard-mh will have a look (if possible an issue would be good to track 🙏)