8000 Check for new Linux and iOS Versions by UsrnmeX · Pull Request #2201 · uazo/cromite · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Check 8000 for new Linux and iOS Versions #2201

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.

Sign up for GitHub

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

Jump to bottom
Draft
wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

Check for new Linux and iOS Versions #2201

wants to merge 1 commit into from
+23 −2

Conversation

UsrnmeX
Copy link
@UsrnmeX UsrnmeX commented Jul 1, 2025
8000

Add Linux and iOS Versions

Description

Please explain here what feature or bugfix these changes are addressing and why they should be included
Sometimes, iOS or Linux versions are even higher than Win/Android. For example, the latest version that was detected here was 138.0.7204.97 even if there is already a version 138.0.7204.119 listed on https://chromiumdash.appspot.com/releases?platform=iOS. But I think there is little differnce, the differences are probably only regarding the iOS Browser, but just to make sure it should be better to also check iOS and Linux, do you think?

All submissions

  • there are no other open Pull Requests for the same update/change
  • Bromite can be built with these changes
  • I have tested that the new change works as intended (AVD or physical device will do)

Format

  • patch subject and filename match (e.g. Subject: Alternative cache (NIK-based) -> Alternative-cache-NIK-based.patch)
  • patch description contains explanation of changes
  • no unnecessary whitespace or unrelated changes

@UsrnmeX
Update build-images.yaml
ab4fd82 
Add Linux and iOS Versions
@UsrnmeX UsrnmeX marked this pull request as draft July 1, 2025 21:07
@uazo
Copy link
Owner
uazo commented Jul 2, 2025

yes, that makes sense.

would you like to do one more thing I would need, always with regard to this action?

@UsrnmeX
Copy link
Author
UsrnmeX commented Jul 2, 2025 via email

@uazo
Copy link
Owner
uazo commented Jul 2, 2025

I would like body.txt to contain the link to the log, in the format

for all indicated sub repos from the json:

  "hashes": {
    "angle": "df15136b959fc60c230265f75ee7fc75c96e8250",
    "chromium": "14f98e519099bc5d4beb1c54e49807a284fe3e63",
    "dawn": "86772f20cca54b46f62b65ece1ef61224aef09db",
    "devtools": "f8dfe8b36e516cef8a5a169e88d16480d8abdc68",
    "pdfium": "cf433ae5520d061db56391155b59b34e67484f39",
    "skia": "a46d5732d9fca93eaec23e502e2eef814b707e6b",
    "v8": "e5b4c78b54e8b033b2701db3df0bf67d3030e4c1",
    "webrtc": "e4445e46a910eb407571ec0b0b8b7043562678cf"
  },

at least also only for v8, which would be in the format

acquiring the current commit from

the value of v8 commit is in https://chromium.googlesource.com/chromium/src/+/refs/tags/138.0.7204.143/DEPS#306
the value of current cromite version is in https://github.com/uazo/cromite/blob/master/build/RELEASE

@UsrnmeX
Copy link
Author
UsrnmeX commented Jul 2, 2025 via email

@PF4Public
Copy link

Do you maybe know if it is possible to avoid this?

I don't think it is possible

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@UsrnmeX @uazo @PF4Public
0