Conversation
wb9688
left a comment
There was a problem hiding this comment.
Why still Windows 10? And did you take this string from an actual instance of Firefox 128 on Windows 10 or just changed the number?
|
Also, we completely skipped 2 ESR versions. Can there be a Github Action to update this automatically, or at least remind us? |
What about adding it to our release process documentation? |
I have seen both user agents with and without the architecture info. We could also change to In that case I'd update TeamNewPipe/NewPipeExtractor#1192 first to check whether this causes any problems.
I also thought about creating a workflow for that. But that should happen in the extractor because user agent changes should be checked there. I don't think that updating the UA should be part of the release process because a faulty UA could brake stuff. |
|
Wht not using the User-Agent of ESR build of Firefox for Linux? |
|
We are always using the ESR version. I should have specified this. The current ESR version is 128 |
|



What is it?
Description of the changes in your PR
Updates the user agent used by the downloader to retrieve files to a current version
Related PR
See TeamNewPipe/NewPipeExtractor#1192
APK testing
The APK can be found by going to the "Checks" tab below the title. On the left pane, click on "CI", scroll down to "artifacts" and click "app" to download the zip file which contains the debug APK of this PR. You can find more info and a video demonstration on this wiki page.
Due diligence