Known addons can update without making PR

Hi there, hope you are all well!

The Garry's Mod addon was last updated through a PR at LLS-Addons on October 3rd 2024. That was version v0002. Since then some new versions have been published to our library repo, however at the time of writing I have yet to make a PR to merge them into LLS-Addons.

Despite not having had a PR (and thus no manual validation by @carsakiller) the newer versions show up and can be switched to:

I remember reading somewhere that the manual process of updating an addon through PR is a sort of security/sanity check. For that reason I don't believe this is intentional

Note that selecting the 'latest' version will still result in the LLS-Addons version to be chosen (for gmod: v0002)

Details

• Using VSCode Extension 3.13.5
• Windows 10
• git version 2.44.0.windows.1
• Webvue version v0.2.0

[2025-01-11 12:03:47] |  VERBOSE  |       Command      | Executing "setVersion" ({"command":"setVersion","data":{"name":"garrysmod","version":"v0006"}})

Commencez par reproduire la commande setVersion avec l'addon Garry's Mod et retracez la manière dont les versions de l'addon sont découvertes et sélectionnées dans l'extension VSCode. Vérifiez pourquoi les releases plus récentes que la version de LLS-Addons deviennent sélectionnables sans pull request. Le travail est terminé lorsque les versions non fusionnées ne peuvent pas être sélectionnées, tandis que latest continue de se résoudre vers la version validée v0002.