Skip to content
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

Test pinning extensions #172034

Closed
3 tasks done
sandy081 opened this issue Jan 23, 2023 · 0 comments
Closed
3 tasks done

Test pinning extensions #172034

sandy081 opened this issue Jan 23, 2023 · 0 comments

Comments

@sandy081
Copy link
Member

sandy081 commented Jan 23, 2023

Refs: #63903, #157079

Complexity: 5

Create Issue


Make sure you have extension autoupdates enabled and try pinning extensions to a specific version using following UI. Make sure extensions are not getting auto updated after pinning.

  • From CLI : Install a specific version using following format - code-insiders --install-extension eamodio.gitlens@13.1.1
  • From Extensions UI - Use *Install Another Version... action in the context menu of the installed extension.
  • Make sure the pinned version is synced across VS Code instances - Use Settings Sync feature to test this. To have different instances of VS Code on same machine, open VS Code from CLI using different user-data-dir and extensions-dir. Eg: code-insiders --user-data-dir <path> --extensions-dir <path>
  • Export and Import the profile with the pinned extension and make sure in the imported profile, extension is still pinned. Export and Import profile actions are available in the global activity context menu (gear).
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants