SyMenu Forum

SyMenu

 

Home ▶ SyMenu Plugins

Everything related to SyMenu plugins: discussion, development, documentation and release

Github SPS Updater - Updates & Add apps Messages in this topic - RSS

ronen1n
ronen1n
Posts: 33


9 days ago
ronen1n
ronen1n
Posts: 33
[Plugin] GitHub SPS Updater & Community Publisher

A plugin for SyMenu that automatically finds and applies updates to apps in your custom suites, lets you add new apps easily, and allows UGMFree uploaders to sync and publish community .sps packages directly to SyMenu servers.

Plugin Features

Adding apps:
  • Add from GitHub: Paste a repo or release link (owner/repo or full URL) — auto-detects version, release date, asset, main .exe, and extracts the icon.
  • Add by direct download link: Paste any .zip, .7z, or .exe URL.
  • Add from PortableApps library: Search and add apps directly from the offline PortableApps catalog into your custom suite.
  • Icon support: Auto-extracts icons from executables/archives, or browse any custom image (.ico, .png, .jpg, .bmp — auto-converted to 16×16 Base64).
  • Auto-configured metadata: Automatically fills in publisher, description, and SPS schema fields (Creative Commons 4.0 license, category).
Updating apps:
  • Auto check & update via GitHub: Tracks upstream releases, tags, and asset naming patterns.
  • Auto update via Webscrape rules: Regex-based scraping for apps without GitHub (scrapes version from download page + downloads via template).
  • NirSoft & JetBrains updates: Built-in update tracking for NirSoft tools and JetBrains standalone products.
  • Background startup check: Can check for updates quietly on SyMenu startup (configurable interval) with tray notifications.
  • 100% Native SyMenu updates: The plugin only updates the local .sps definition files. SyMenu's native updater handles the actual downloading, unpacking, and installing.
UGMFree SPS Publisher (for uploaders):
  • Check uploader apps: Compares your local custom suite packages against the packages currently live on UGMFree servers under your account.
  • One-click publish: Push updated .sps definitions directly to UGMFree without needing external tools.
  • Schema validator: Pre-checks categories, packer formats, executable paths, and required metadata before uploading to prevent server errors.
Security & Verification:
  • VirusTotal integration: Automatically queries VirusTotal API v3 for scan ratios and embeds report permalinks.
  • Detection limit guard: Blocks updating a package if VirusTotal detections exceed your threshold.
Menu & Suite Tools:
  • Prune menu shortcuts: Keep alternative executables you don't use (e.g. 32-bit versions, CLI variants, or secondary companion tools in the same app) from being re-added to your menu every time the app updates.
  • Remove duplicate shortcuts: Clean up duplicate entries across suites.
  • Merge PortableApps: Import and link apps from an existing PortableApps directory structure.
RequirementsInstallation
  • Download.
  • Extract the folder into:<SyMenu>\Plugin\SyMenuGitHubUpdater\
  • Restart SyMenu.
  • Access via Plugin → GitHub SPS updater.

  • Optional Settings

    Inside the plugin window, click Settings...:
    • GitHub Token: Recommended to increase rate limits from 60 requests/hour to 5,000/hour.
    • VirusTotal API Key: If you want automated malware scanning before updating.
    • UGMFree Account: Enter your forum username & password if you want to publish community .sps packages.

    This post and most of the plugin done by AI so if you need any other explanation for what the plugin doing or want any change that will make sense please let me know
    This plugin approved by SyMenu author for pro users
    This plugin still has some bugs so use at your own risk
    The idea for this plugin is to make adding and updating apps to SyMenu easier
    Please tell me what you think


    Edit:

    - Auto-detect vendor APIs & direct releases: Out of the box, popular standalone tools (such as JetBrains' dotPeek, IntelliJ Community, PyCharm Community, NirSoft tools, etc.) are automatically mapped to their official vendor update APIs by name without requiring a GitHub link or manual regex configuration.


    ### Changelog — Version 2.0.1

    **Fixes & UI Improvements:**
    * **SyMenu Auto-Hide Fixed:** Resolved an issue where SyMenu stayed stuck on-screen and stopped auto-hiding on losing focus. The plugin now explicitly dismisses the SyMenu dropdown upon launching and runs its window on an isolated thread, leaving SyMenu's taskbar auto-hide behavior completely untouched.
    * **Settings Dialog Layout:** Fixed a layout issue where the "Save" and "Cancel" buttons were cut off at the bottom on initial opening. The dialog now defaults to a taller size and includes vertical auto-scrolling for smaller displays.
    * **PortableApps Directory Layout & New Suite Creation:**
    * Fixed an issue where the "Visit website" button was pushed to an invisible second row under high-DPI scaling.
    * Added the ability to enter a **new suite name directly** in the "Target Suite" dropdown (selecting an existing suite or typing a new suite to install to).
    * Fixed dark theme rendering for editable dropdowns (eliminated white background flashing/selection glitches and restored the dropdown arrow).
    * **SPS Community Publisher:** Fixed overlapping text between the account status label (`Account: (not configured)`) and the `(Settings)` link.
    * **Expanded Archive Compatibility (RAR / ZIP / 7Z):** Fixed check error `PackerFormat 'zip' does not match the download '.rar'`. SyMenu extracts RAR, ZIP, and 7Z interchangeably with 7-Zip; the updater now treats archive formats interchangeably and automatically updates the `<PackerFormat>` tag in the definition to match upstream.
    * **Expanded Vendor API Rules:** Added automatic JetBrains API tracking for dotPeek, IntelliJ IDEA Community Edition, PyCharm Community Edition, and JetBrains Gateway.



    Download:
    SyMenuGitHubUpdater-2.0.6 | F2H

    edited by ronen1n on 15/11/2026
    link
    Gianluca
    Gianluca
    Administrator
    Posts: 1409


    3 days ago
    Gianluca
    Gianluca
    Administrator
    Posts: 1409
    Dear ronen1n,

    I think there is a misunderstanding here.

    SyMenu and the plugin have different goals.

    SyMenu updates are intentionally based on human validation and publication. An SPS becomes available to all users only after an editor decides to publish it. This design has several advantages: quality control, source verification, licensing checks, VirusTotal verification, package structure validation, and support for any download source, not only GitHub.

    The plugin follows a different approach. Its goal is to detect and apply updates much faster by relying on automation.

    Both approaches are valid, but they naturally produce different results.
    If the plugin chooses to update SPS definitions that belong to the SyMenu or NirSoft suites before the corresponding official definitions are published, temporary version mismatches are expected, and a loop of continuous updates and downgrades may occur until the SyMenu definitions match those generated by the plugin. In some cases, this may never happen.

    How should those mismatches be handled?
    Not by SyMenu, because it has to follow its own logic and workflow.
    Not by the plugin either, because it has to follow its own logic and goals.
    IMO, the only way to solve this is to prevent the two logics from overlapping.
    And to prevent this kind of doubt, should I stop maintaining GitHub-based SPS files in the official suites because the plugin now exists?
    I don't think so. The plugin is still relatively new, not every user relies on it, and it still needs time to prove its robustness, reliability, and long term accuracy.
    Moreover, I still don't understand how a new GitHub SPS managed by the plugin should reach users for the first time. If it is distributed through the official suites, we are back to the overlap problem. If it is not distributed through the official suites, how does it initially reach the users? Well this is entirely obscure for me.

    Custom suites are a different story because there is no official editor workflow behind them, which is why I see much more value in the plugin operating there.

    What happens if you are not satisfied with the release pace of a SyMenu suite application?
    For example, for Thunderbird Portable I chose to follow the ESR releases rather than every available version. If Thunderbird Portable were available on GitHub, you could choose whether to manage it within its original suite or manage it through the plugin. The latter approach suggests placing it in a custom suite.
    This is how I would operate, but every user is free to work the way they prefer.
    If you want to suggest a workaround that enables a different scenario, you are free to do so.


    Remember when I was talking to you about the architectural choices you took for the plugin?
    This is one of the friction points I had in mind when we previously discussed the plugin scope.
    The plugin can certainly choose different directions from what I suggested, but in that case these kinds of conflicts are expected and should probably be addressed at the plugin level rather than at the SyMenu level.


    A big element of confusion comes from this sentence:
    ronen1n wrote:
    you say it's simple to limit the plugin a lot to just update github apps and apps that not in symenu or not in nirsoft but also want new apps to get into symenu list so what's the point?

    Creating new SPS for the official suite, submit them, and enriching the SyMenu echosystem can be a nice thing the plugin can bring on the table.

    But please don't confuse the role the plugin could have for an end-user and the role it can have for an editor.

    If you are an editor and decides to go with the plugin to create/update your GitHub SPS for the official suite, please be my guest.
    You have to grant the same high level quality I expect from any editor and take responsability of your SPS.
    So you can use the plugin to get help with updates and use it to load the new/updated SPS to the cloud.
    But from there on, I don't care how you worked, your work has to meet the same quality standards as any other SPS published through SyMenu. The SyMenu community deserves the highest level of validation we can reasonably provide.

    On the other hand you have the users.
    Why should an average user perceive the plugin as more useful than the standard automatic updates?
    In most cases, there is no compelling reason. The users want a trustable system that takes care of their program automatically. Most users are more interested in stability and reliability than in receiving updates a few days earlier.
    An advanced user may find it useful to add software that is not yet available in the suites, and the plugin enables exactly this kind of customization but why a normal user would have to mix the official suite with custom SPS? I don't see the reason.

    There's a third scenario, where an editor want to use the plugin to create a custom, publicy-available, suite (sl23 is working on a suite like this). The editor probably can choose to use the plugin to create the SPS and suggest their users to use the plugin to get the updates. So they publish the starting definitions, the users download it, and from then on the plugin takes the lead.

    And probably there's many other use case possible. But again, these are the kinds of design considerations that inevitably emerge once a tool starts being used in different ways by different users, and, above all, this kind of discussion is not suitable for this forum (I imagine nobody except the two of us read all this long post).
    To be fair, these are exactly the kinds of questions I hoped we would address during the design phase.
    They don't necessarily invalidate the plugin, but they become increasingly important as the plugin starts being adopted by a wider audience.

    edited by Gianluca on 16/11/2026
    +2 link
    Gianluca
    Gianluca
    Administrator
    Posts: 1409


    7 days ago
    Gianluca
    Gianluca
    Administrator
    Posts: 1409
    A great addition for the next version would be an About entry in the Tools menu or at least an indication of the plugin version in the settings, as it is currently impossible to determine which version is running unless you inspect the dll file through the Windows file properties dialog.
    Another issue: I noticed that the plugin remembers the last applied filter, but the filter text box remains empty. As a result, I end up with a filtered grid without knowing which filter is currently active.
    As a related improvement, a visual indicator showing that one or more filters are active could also be useful.
    +1 link
    Gianluca
    Gianluca
    Administrator
    Posts: 1409


    2 days ago
    Gianluca
    Gianluca
    Administrator
    Posts: 1409
    Dear ronen1n,

    I think we simply have different goals.

    You built the plugin primarily to solve your own problem, and from what I can see it does that very well.
    My interest was different: I was trying to understand whether some of the ideas behind the plugin could evolve into products suitable for the broader SyMenu ecosystem.

    Sometimes these two goals overlap, sometimes they don't.

    As I said from the beginning, I think some of the ideas in your plugin have great value.
    We simply disagree on how they should evolve and above all how they should interact with the official suites.
    That's perfectly fine.

    If the plugin works the way you want it to, then you have achieved your goal.

    The forum thread should absolutely stay where it is.
    Users can test the plugin, share feedback, suggest improvements, and decide for themselves whether it fits their needs.
    Also, for what it's worth, I'm currently using the plugin myself for some software in my custom suite and I expect I'll continue using it because, in that scenario, I think it does a very good job.
    So please keep sharing new versions if you decide to continue developing it. I'll be happy to follow its evolution and test new releases.
    And if, at some point in the future, you ever feel like revisiting some of these design discussions, you know where to find me.
    The door is always open.

    Good luck with the project.
    +1 link



    UGMFree © 2002-2026
    PayPal BTC TON