microsoft / microsoft/winget-pkgs

[Package Issue]: Git.Git uninstalls extensions during upgrade

Open
#95,162 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Issue-Bug
Dominant language
No language data
Stars
11.1k
Forks
9.7k
Avg merge
1h 32m
Merged PRs (30d)
376

Description

Please confirm these before moving forward
  • I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
  • I have not been informed if the issue is resolved in a preview version of the winget client.
Category of the issue

Installation issue.

Brief description of your issue

When performing an upgrade to the Git.Git package, an uninstall is performed which removes any extensions, even if they are also installed using winget. Most noteworthy being Microsoft.GitCredentialManagerCore and GitHub.GitLFS. This forces you to keep a list of all extensions and reinstall them manually after any upgrade, and realistically prevents you from ever running upgrade --all as it risks breaking things.

Steps to reproduce
winget install Git.Git -v 2.39.0
winget install Microsoft.GitCredentialManagerCore
winget upgrade Git.Git
Actual behavior

extensions are uninstalled although any configurations in .gitconfig remain.

Expected behavior

extensions to remain in-place or be automatically reinstalled after a git upgrade so functionality remains.

Environment
Windows Package Manager v1.3.2691
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.22623.1245
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.18.2691.0

Logs: %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir

Links
---------------------------------------------------------------------------
Privacy Statement   https://aka.ms/winget-privacy
License Agreement   https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage            https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale
Screenshots and Logs

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the documented commands with Git.Git 2.39.0 and Microsoft.GitCredentialManagerCore, then inspect the Git.Git package upgrade behavior in winget-pkgs. Done means upgrading Git.Git no longer removes winget-installed extensions, or restores them automatically while preserving the existing .gitconfig settings.

Written by the indexing model from the issue text.

Assessment

Tech stack
git
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.