chromium/132.0.6834.159 package update

[octo-sts]

[octo-sts]

⚠️ EXPERIMENTAL

Please use 👍 or 👎 on this comment to indicate if you agree or disagree with the recommendation.

To provide more detailed feedback please comment on the recommendation prefixed with /ai-verify:

e.g. /ai-verify partially helpful but I also added bash to the build environment

Gen AI suggestions to solve the build error:

• Detected Error: "FAIL Expected commit d0b491d2f2c17c0f56d43ed1b95c803eb000a9b1 for 132.0.6834.159, found 2d77d3fc4452661469b78f115e0aed4d71269739"

• Error Category: Version/Commit Mismatch

• Failure Point: Git checkout step verification of expected commit hash

• Root Cause Analysis: The commit hash specified in the melange YAML doesn't match the actual commit hash for the tagged version 132.0.6834.159

• Suggested Fix:
Update the expected-commit in the git-checkout step to match the correct commit hash:

  - uses: git-checkout
    with:
      repository: https://chromium.googlesource.com/chromium/src.git
      tag: ${{package.version}}
      depth: 1
      expected-commit: 2d77d3fc4452661469b78f115e0aed4d71269739
      destination: /home/src

• Explanation: The build system is correctly fetching the tagged version but finding a different commit hash than expected. This is a safety check to ensure we're building exactly the version we intend to build. Updating the expected-commit to match the actual commit hash for this tag will resolve the verification error.

• Additional Notes:

• This is a common issue when updating package versions as commit hashes need to be synchronized
• The correct commit hash can be verified using:
  git ls-remote https://chromium.googlesource.com/chromium/src.git refs/tags/132.0.6834.159
• Chromium's release tags are signed and verified, so this commit hash represents the official release

• References:

• Chromium Release Tags: https://chromium.googlesource.com/chromium/src.git/+refs
• Chromium Version Numbering: https://www.chromium.org/developers/version-numbers/