-
Notifications
You must be signed in to change notification settings - Fork 261
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Default Extensions If Installed Locally: Install pre-release if local extension is pre-release #9840
Comments
Dupe of microsoft/vscode-copilot-release#1129 which was resolved. Had the same problem. |
Even though I'm using the pre release version, every time the container is built, it installs a non pre release version of the extension, so I'm back to this issue with every build. How do we enforce a dev container with vs insider to always use the pre release version of the copilot extension? I'm lost. It's leading to various other side effects other than this. |
Thank you all for the continued feedback. My understanding is the next step from the related issue was to open an issue in https://github.com/microsoft/vscode-remote-release/issues since this is likely a Dev Containers extension issue, and include the repro steps of your setup (i.e. what does your devcontainer.json look like, how are you connecting via the Dev Containers extension) so that we can try it out. Did folks open that issue and I might've missed it? If so, could you please share it here? Thanks so much! |
Still plagued with this issue, I've to upgrade copilot and copilot chat to pre-release everytime i run dev container, to get them working. Here's probably how to repro it in devcontainer.json
And here's my full dev container json in case it help debug: https://gist.github.com/epicwhale/cd13a77c17ca24ff37c29cf55994de39 |
I have this same issue. |
also encountering this |
@bamurtaugh Thanks for the ping, I'll continue here. The I will fix this by remembering if the extension is installed as pre-release locally. This will also benefit the more general case where users are working with a pre-release version locally and expect pre-release to be used in the container too even if the devcontainer.json lists the stable release. (Assuming the user's local choice takes precedence over the devcontainer.json potentially shared with a team.) |
Verification in next Dev Containers pre-release version:
|
Version: 1.89.0-insider
Commit: 063d715c4504380317f9ca8eefc602d71e56adb5
Date: 2024-04-19T06:04:15.360Z
Electron: 28.2.8
ElectronBuildId: 27744544
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Darwin arm64 23.4.0
Steps to Reproduce:
The text was updated successfully, but these errors were encountered: