update-checker
Here are 109 public repositories matching this topic...
-
Updated
Jan 19, 2021 - Java
-
Updated
Mar 25, 2022 - Python
-
Updated
Jun 7, 2022 - Go
-
Updated
Apr 25, 2022 - Java
-
Updated
Apr 7, 2021 - Swift
-
Updated
Aug 25, 2020 - Kotlin
-
Updated
May 31, 2022 - Rust
-
Updated
May 18, 2022 - PHP
-
Updated
May 12, 2020 - C#
-
Updated
Jun 6, 2022 - JavaScript
-
Updated
Aug 20, 2021 - Go
Certain projects use the release tag in the archive name, eg awesome-package_0.1.2_linux_amd64.tar.gz, and I seem to recall some that even use it in the binary name too (not that I think the latter is a good idea).
My suggestion is to allow some basic go templating on both the Provider ArchiveName and Updater .ExecutableName of at least some common variables, such as {{.Tag}} {{.GOOS}}`
-
Updated
Mar 30, 2022 - Go
-
Updated
Dec 1, 2021 - Shell
-
Updated
May 20, 2022 - C++
-
Updated
May 29, 2022 - Go
-
Updated
May 27, 2022 - PHP
Is your feature request related to a problem? Please describe.
It's a feature request.
Describe the solution you'd like
Optional update profile configuration for each plugin to avoid update errors for premium plugins.
Describe alternatives you've considered
No idea.
-
Updated
Jun 2, 2022 - AutoHotkey
-
Updated
Apr 3, 2022 - Go
-
Updated
Jul 17, 2020 - Java
-
Updated
Jun 6, 2022 - Python
-
Updated
Mar 13, 2022 - JavaScript
-
Updated
Jun 6, 2022 - Python
-
Updated
Jun 5, 2022 - PHP
-
Updated
Nov 1, 2017 - PHP
-
Updated
May 19, 2022 - Java
-
Updated
Mar 25, 2022 - PowerShell
Improve this page
Add a description, image, and links to the update-checker topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the update-checker topic, visit your repo's landing page and select "manage topics."


The (still undocumented) feature is great for our purpose, but can you add the same functionality to the post-update hook (in the same manner, of course)?
I have added a script to the post-update to check the database-version. If they not match, the script returns exit 1. It would be great if the post-update hook could log a error- or warning-message, so the slack-notification gets a message (l