Upgrade from v29.0.2 → v29.1.0?

[sjbrouillard]

I apologize if this is a duplicate. I can't find one, but feel free to just point me to the duplicate if it's out there.

I've always installed OMP using winget, and for the most part have had no issues. I'm currently on 29.0.2 and am getting the following message each time OMP starts up.

A new release of Oh My Posh is available: v29.0.2 → v29.1.0
To upgrade, run: 'oh-my-posh upgrade'

That happens all the time when it's part of your profile and you're running Claude Code sessions, since it starts a new POSH session every time it executes POSH commands. Because winget loads the MSIX version of OMP, if I try to upgrade it via oh-my-posh upgrade, I of course, get the ❌ upgrade is not supported when installed as a MSIX package message. Unfortunately, winget doesn't seem to be updated yet. I think it's been two weeks, which, from my recollection is unusual for it to take that long. I'm not complaining, I'm just checking in. I tried uninstalling via winget and reinstalling via the manual POSH script method. Doing that, I noticed two things.

1. That method also installs OMP via MSIX, so no real difference on the ability to update via the command line for via auto-update.
2. That also seems to have installed 29.0.2. That's what I get when I run oh-my-posh --version.

I want to be clear, this discussion is not meant to be a complaint, nor is it critical that this be addressed immediately. I'm not having any issues that are significant. This, as much as anything, is for me to understand what's happening and for me to potentially point it out, in case this is something that fell through the proverbial cracks.

Having said that, I have a couple of questions.

1. Am I missing something? Is OMP always installed via MSIX and using the command or auto update in Windows just not an option?
2. If there's a way to install to enable auto update, I think that might be worth doing in my case, but how to do that? I don't use Chocolately anymore, winget meets my needs and I'm not looking to add an additional package manager. Is that the only way, or am I just missing something?
3. Regardless, in the past winget seemed to be updated really quickly. Is this a known issue that I'm just not seeing, or are things just a bit behind?

Thanks in advance for any insight you all might have. I appreciate your time. If I'm just missing something, feel free to just add a link, smack my hand, and tell me where the part of the manual I didn't read is. RTFM with a link to the appropriate place, is a perfectly acceptable answer. I will read it, hang my head in shame for the prescribed mourning period, and move on.

Cheers,

Steve

[K2ouMais]

I also use oh-my-posh on WSL and with Powershell.

The Linux version seems to be updated without a problem, but using winget to update on powershell doesnt seem to work.

I am also on an older version of oh-my-posh.

WSL:

Powershell:

[K2ouMais]

It seems something got fixed and oh-my-posh can be updated in Powershell again.