alefragnani / vscode-project-manager

Project Manager Extension for Visual Studio Code
GNU General Public License v3.0
1.89k stars 225 forks source link

[BUG] - "What's new ..." always displays and sometimes it's outdated #677

Closed tyler36 closed 1 year ago

tyler36 commented 1 year ago

I've been a long-time fan of this extension however recently it is driving me crazy.

Everytime I open a project it displays a "What's new ... 12.7" Everytime I close a project it displays a "What's new ... 12.0"; yes, a different, older version. Everytime I re-open a project it a "What's new ... 12.7". Everytime I open a project on Gitpod, it displays a "What's new" popup.

Ideally, I'd love to disable this "feature" completly. However I know from searching for duplicate issues that you have no intention of allowing this.

But seeing this pop up every single time I open AND close a project is excessive. The fact that they are different version hints there might be something else going on.

Environment/version

Steps to reproduce

  1. Open up an exisiting project, it displays a "What's New in Project Manager 12.7" new-12-7

  2. Close "What's new" tab.

  3. Close project via "File | Close Remote connection." It displays a "What's New in Project Manager 12.0" new 12-0

  4. Open previous project, it displays "What's New in Project Manager 12.7" again.

reggiepy commented 1 year ago

I have the same problem

alefragnani commented 1 year ago

Hi @tyler36 ,

I could reproduce the broken What's New page. It was a missing update and it will be available in the next release at the end of the month.

The outdated behavior, on the other hand, I couldn't reproduce. No matter if the project is located locally or WSL, if the extension is installed in the host (regular) or inside the WSL (using remote.extensionKind setting), it always display the current (newer) release.

I think it displays 12.0 because you are using Gitpod or some VS Code alternative like VS Codium, because that's the version number which is currently unofficially available in open-vsx. The extension is not supported there yet, but will be, and can be tracked in #458 . I had planned to release a couple of months ago but couldn't focus back then, but things are getting better and I'll be able to have better cadence on releases.

Hope this helps