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

Adding tools to "Automatic hash update" process? #5833

Closed
M1kep opened this issue Jan 1, 2021 · 9 comments
Closed

Adding tools to "Automatic hash update" process? #5833

M1kep opened this issue Jan 1, 2021 · 9 comments
Labels
Issue-Docs It's a documentation issue that really should be on MicrosoftDocs
Milestone

Comments

@M1kep
Copy link
Contributor

M1kep commented Jan 1, 2021

I'm interested in how an application can be added to to the Automatic Hash Updates that wingetbot performs?

@ghost ghost added the Needs: Triage label Jan 1, 2021
@denelon denelon added Issue-Docs It's a documentation issue that really should be on MicrosoftDocs and removed Needs: Triage labels Jan 2, 2021
@ghost ghost added the No-Recent-Activity No activity has occurred on this work item for seven days. label Jan 9, 2021
@ghost
Copy link

ghost commented Jan 9, 2021

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 7 days of this comment.

@M1kep
Copy link
Contributor Author

M1kep commented Jan 10, 2021

Adding some "Author Feedback" to keep this open.

@ghost ghost removed the No-Recent-Activity No activity has occurred on this work item for seven days. label Jan 10, 2021
@jedieaston
Copy link
Contributor

jedieaston commented Jan 11, 2021

It does it automatically if the hash doesn't match for the same URL. For example, Google doesn't post a new URL for each installer for Chrome, so if the bot detects that the hash for the always up-to-date installer URL has changed, it fixes the manifest.

(as I understand it, since the code isn't available yet).

@M1kep
Copy link
Contributor Author

M1kep commented Jan 13, 2021

@jedieaston id agree it was automatic, but the kubectl package was using the "latest" format as well and was overlooked. This leads me to believe there is some specific format or a registration, for lack of a better word, that needs to happen.

After reviewing, it actually wasn't using a latest.yaml. I could add one as a test, but may be preferred to get confirmation if that's the correct method.

Ref: #5831 #5832

@ghost ghost added the No-Recent-Activity No activity has occurred on this work item for seven days. label Jan 20, 2021
@ghost
Copy link

ghost commented Jan 20, 2021

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 7 days of this comment.

@M1kep
Copy link
Contributor Author

M1kep commented Jan 20, 2021

"Author Feedback"

@ghost ghost removed the No-Recent-Activity No activity has occurred on this work item for seven days. label Jan 20, 2021
@M1kep
Copy link
Contributor Author

M1kep commented Jan 20, 2021

@denelon is there someway to flag this issue so I don't have to provide "author feedback" every week?

@KevinLaMS
Copy link
Contributor

@M1kep it should be fixed. Sorry about that.

@denelon
Copy link
Contributor

denelon commented Oct 19, 2022

This issue has been resolved for quite some time. I'm going to go ahead and close this.

@denelon denelon closed this as completed Oct 19, 2022
@denelon denelon added this to the 1.7 Packages milestone Nov 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Docs It's a documentation issue that really should be on MicrosoftDocs
Projects
None yet
Development

No branches or pull requests

4 participants