Skip to content
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

Add automatic update checker #63

Merged
merged 6 commits into from
Jun 23, 2024
Merged

Conversation

randshell
Copy link
Contributor

This change automatizes syncing new Deezer releases, keeping the Linux version closer to the latest official release. I've also updated the current version to the latest one as of now, which is 6.0.150.

A GitHub Secret is needed for the FlatHub Bot so that it can automatically commit the new update and open a PR.

This soultion uses the Flathub Bot since it is easy to implement and works well for this use case. A GitHub Action is set to make it run once a week.
Makefile was updated as well to reflect the changes.
It is compared against the FlaHub's bot calculated SHA256
Compared to deezer.com, e-cdn-content.dzcdn.net does not support resuming a download
@aunetx
Copy link
Owner

aunetx commented Jun 23, 2024

Hello, thank you very much for your work, this is incredible! I wanted to do something similar for quite some time, but never knew how to...

I've got a little question (I don't know that much about github actions, sorry if that's dumb): about the github token, I created a personal access token with the name GITHUB_TOKEN with the required permissions, but I'm not sure that's enough to make this work... So I'm merging this, but if that somehow fails then we will know why!

@aunetx aunetx merged commit 755bd40 into aunetx:master Jun 23, 2024
1 check passed
@randshell
Copy link
Contributor Author

Hi @aunetx! You're welcome. I was actually pretty excited about contributing here. Thank you for maintaining Deezer for Linux. 😄

Regarding the GITHUB_TOKEN, I read more about it and it turns out that it is automatically created by Github as a GitHub App on a per repo bias, once it is specified inside a workflow file. I think at this point it should be safe to delete the personal access token you created and still see if there is any fail. xD

@randshell randshell deleted the update-checker branch June 24, 2024 05:32
@randshell
Copy link
Contributor Author

Oh, I've also just found out that scheduled workflows get automatically disabled if there is no repo activity in 60 days.

If I understand it right, the bot creates a new branch and commits the new Deezer version there, which technically should be repo activity. In other words, as long as there is a new Deezer update every 60 days, this repo should require no manual intervention haha.

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

Successfully merging this pull request may close these issues.

2 participants