Github.dev currently ships pre-release GitHub Pull Requests Plugin 0.158.0 which is incompatible with Github.dev pinned VS Code 1.128.1

[andraleia]

🏷️ Discussion Type

Bug

Body

Summary

There appears to be a deployment/versioning mismatch in the GitHub repository experience on github.dev / vscode.dev.

When opening a GitHub repository (for example by pressing . on any repository or pull request), the editor automatically provisions GitHub Pull Requests v0.158.0. However, that extension declares a minimum VS Code engine version of ^1.129.0, while the hosted editor is currently running VS Code 1.128.1.

As a result, the GitHub Pull Requests extension is immediately disabled, breaking one of the primary workflows of github.dev: working with and reviewing pull requests.

Environment

• Entry point: Press . on any GitHub repository or pull request
• Editor: github.dev / vscode.dev
• VS Code version: 1.128.1
• Automatically provisioned GitHub Pull Requests extension: 0.158.0

Extension error:

Extension is not compatible with Code 1.128.1. Extension requires: ^1.129.0.

Steps to Reproduce

1. Open any GitHub repository or pull request.
2. Press . to open it in github.dev.
3. Open the Extensions view.
4. Select GitHub Pull Requests.

Actual Behavior

The extension is disabled because its engine requirement exceeds the version of VS Code currently deployed by github.dev.

Since the extension is disabled, GitHub Pull Request functionality is unavailable.

Additionally, there is no supported way to downgrade to a compatible version from within the GitHub repository environment:

• Install Specific Version... is disabled.
• Install Another Version... is unavailable.

Because the automatically provisioned extension behaves as a built-in extension in this environment, users cannot replace it with a compatible release.

Expected Behavior

The version of GitHub Pull Requests automatically provisioned for GitHub repository workspaces should always be compatible with the version of VS Code deployed by github.dev.

Additional Observations

This appears to be specific to GitHub repository workspaces rather than vscode.dev itself.

When opening https://vscode.dev directly (without opening a GitHub repository):

• The latest stable version available is 0.156.x.
• The latest pre-release version available is 0.157.2026070710.
• Both are selectable through the normal extension UI.

However, when opening a GitHub repository, the environment automatically provisions 0.158.0, which does not appear to be publicly available through either:

• the Visual Studio Marketplace, or
• the GitHub Pull Requests extension Releases page.

This suggests the GitHub repository experience is sourcing the extension from a different deployment channel than the public Marketplace.

Workaround

The only workaround I have found is:

1. Open https://vscode.dev directly (without opening a GitHub repository).
2. Install GitHub Pull Requests 0.156.x.
3. Afterwards, open a GitHub repository or pull request.

The compatible version is then retained in browser storage for that browser profile and functions normally.

This workaround is not discoverable, and it is unavailable to users who begin in the GitHub repository experience because the compatible version cannot be installed or selected from there.

Suggested Resolution

Any of the following would resolve the issue:

• Update the github.dev VS Code runtime to a version compatible with the automatically provisioned extension.
• Provision a compatible version of GitHub Pull Requests until the runtime is updated.
• Do not automatically replace a compatible installed version with an incompatible one when opening GitHub repository workspaces.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐