Skip to content

upgrade_only won't work on some repositories #124

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
zhaose233 opened this issue Feb 8, 2025 · 1 comment
Open

upgrade_only won't work on some repositories #124

zhaose233 opened this issue Feb 8, 2025 · 1 comment

Comments

@zhaose233
Copy link

zhaose233 commented Feb 8, 2025

I configured eget to keep tracking several softwares releasing single jar files up-to-date, but some of them won't work, eget keeps claiming it's up-to-date while it's not.
For example, Anuken/MindustryBuilds ,
My config:

[global]
    upgrade_only = true
    github_token = "MY_TOKEN"

["Anuken/MindustryBuilds"]
    download_only = true
    target = "~/Applications/Mindustry/Mindustry.jar"
    asset_filters = ["Desktop"]

["yairm210/Unciv"]
    download_only = true
    target = "~/Applications/Unciv/Unciv.jar"
    asset_filters = ["Unciv.jar"]

and after first time install (if I delete the jar file and run eget again, it will download the latest version), then when I do eget -D as a new build comes out :

Anuken/MindustryBuilds: requested release is not more recent than current version

But for yairm210/Unciv eget works fine, able to pick upgrades.
Is there any issue in my config?

@j-lakeman
Copy link

j-lakeman commented Apr 16, 2025

Might be related to #115

Check out #65 (comment) which "fixed" it for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants