-
Notifications
You must be signed in to change notification settings - Fork 77
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 "fix broken hashes" automation #1270
Comments
Requesting for more information regarding the issue. |
This issue is about extending our current CI to update broken package automatically, similarly as we do with package updates at the moment. What exactly is not clear @PrajeetGuha? |
The CI automation automatically updates package url, version and respective hash. By the term hash of broken packages you mean |
Is it same as this? #91 |
Hey @PrajeetGuha, are you working on it ? I can help out with it. cc: @Ana06 |
@nasirhm I have not started working on it. You can work on it if you want to. |
@Ana06 I would like to work on it. |
@PrajeetGuha we have some URLs that do not include the version. When a tool update happens, the URL stays the same, but the hash changes. This breaks the package as the hash verification fails. This issue is about adding a new automation (or extending the current one) to update the hash when it does not match the current one. You are right it is a duplicate of #91. |
@nasirhm note that this issue requires some knowledge of GitHub Actions, Python, PowerShell and how the project works and is structured. So it may not be the easiest issue to start contributing to the project. But if it is something you find interesting and you want to give it a try, please go for it! Let us know if you plan to work on it, so that otherwise @PrajeetGuha or @sara-rn can work on it. And sorry for the late reply, I have missed this. 😅 |
@nasirhm can you please let us know if you are planing to work on this so that otherwise someone else can start working on it? |
Details
Add automation to automatically update the hash of broken packages, similar to the package update. This automation should only be triggered manually and we should add to the PR description that the update needs to be reviewed.
The text was updated successfully, but these errors were encountered: