How should we think about winget pin

[denelon]

Pin-WinGetPackage isn't an approved verb

We also have it as an experimental feature, so we will look at the PowerShell idoms for experimental features, and make it correctly align to enable the feature in winget via the PowerShell - COM API interface.

I did get the suggestion of "Lock" on the PowerShell community call today.

[SeeminglyScience]

Just to throw out a couple more, one of these is probably what I'd do:

• Lock-WinGetPackage
• Limit-WinGetPackage
• Set-WinGetPackageVersionPin

[denelon]

I'll split these out for a 👍 style vote.

[joelst]

Lock and Limit are valid and correctly describe what is being done. Definitely extra points for being able use standardized verbs that we don't see often enough correctly. I'm just not sure PowerShellers will gravitate towards them.

[denelon]

Lock-WinGetPackage

[denelon]

I think I like this one.

One caveat to note is the package might upgrade itself, other package managers, and the user could still upgrade without going through WinGet.

One of the concepts we thought about is some mechanism to display packages at a newer version than the PIN as a "pin violated" type of indication.

[ALIENQuake]

Even if Lock seems to fit nicely, the description of this verb is "Secures a resource" so the usage context is somehow related to 'security'. Currently, this verb it's commonly used as so. Given the case, I lean towards @joelst proposal.

[denelon]

Limit-WinGetPackage

[denelon]

Good question @ThomasNieto. One approach would be logically setting the "limit" to none or unlimited. I guess the other approach would be to make a pin into a noun and use the other verbs.

[joelst]

Is this still an option open for discussion?
My unbiased opinion 🙄 this Add-WingetPackagePin, Remove-WingetPackagePin was a decent suggestion 😜

I think it mirrors the winget pin syntax while still being in line with PowerShell standards.

It could work like this:

# fictional example, not real syntax
Add-WinGetPackagePin -Package "my-funny-program" -Versions @(">= 1.2.0", "< 2.0.0") -Sources @("internal-enterprise-source-123")
Remove-WinGetPackagePin -Package "my-funny-program"

[ALIENQuake]

There is also a way to keep 'Limit':

New-WinGetPackageLimit -Name "my-funny-program" -SemVersion ">= 1.2.0", "< 2.0.0"
Set-WinGetPackageLimit -Name "my-funny-program" -SemVersion ">= 1.2.1", "< 2.0.1" -Source "internal-enterprise-source-123"
Remove-WinGetPackageLimit -Name "my-funny-program"

[denelon]

• Add "Limit-WinGetPackage" #3234

We can certainly change the title and incorporate this suggestion.
Throw some comments on the issue and we'll see if we get pushback or consensus. 😊

[Umrhedar]

• Add "Limit-WinGetPackage" #3234

We can certainly change the title and incorporate this suggestion. Throw some comments on the issue and we'll see if we get pushback or consensus. 😊

I like the way it is done with "apt" in debian/ubuntu like: "apt-mark hold " so with winget and powershell I would suggest
winget --hold -Name/ID <app-name/-id> -Version <>=x.y.z
winget --unhold -Name/ID <app-name/-id> -Version <>=x.y.z
winget --list-hold

or like
Set-WinGetHold -add -Name/ID <app-name/-id> -Version <>=x.y.z
Set-WinGetHold -remove -Name/ID <app-name/-id> -Version <>=x.y.z
Get-WinGetHold

At the moment I just use a script with all App-IDs I want to upgrade instead of using --all because there is one userfull little bugger driving me crazy with the new version... On my linux systems the hold feature is my saviour in many situations until I have time to change something or a problem is fixed. It's a good feature when used with consideration. I'm looking forward to see/use that feature in winget.

[denelon]

Set-WinGetPackageVersionPin

[denelon]

This one might cause a bit of a headache with autocomplete.

[joelst]

I think it ok to use New- and Remove- or Set- and Reset- 

Since the cli command is winget pin **add** it really should be Add- and Remove- that way PowerShell is in line with the cli. This will make it easier to use.

I like Lock- however, it is not used very often, so it may not be easy to discover, which is ironic since the standardized verbs are meant to make it easy to discover.

The noun would be something like WinGetPackagePin 

My suggestion is the following:

• Add-WinGetPackagePin - Add a pin to the specified package
• Remove-WinGetPackagePin - Remove the pin from the specified package
• Get-WinGetPackagePin - Return a list of all pins, or the pin for a specified package.

[cgerke]

@joelst suggestions seems most logical and easily discoverable for those new to powershell.

[SeeminglyScience]

I'd actually lean towards these tbh

[denelon]

• Add "Limit-WinGetPackage" #3234