lua-luv/1.50.0.1 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:

warning: Could not find remote branch v1.50.0-1 to clone.
fatal: Remote branch v1.50.0-1 not found in upstream origin

• Error Category: Version/Git Checkout

• Failure Point: Git checkout step failing to find the specified tag

• Root Cause Analysis: The tag format in the git-checkout step doesn't match the actual tag format in the upstream repository. The repository uses tags like "1.50.0-1" without the "v" prefix, but the checkout is trying to use "v1.50.0-1".

• Suggested Fix:
Modify the git-checkout step in the pipeline to remove the "v" prefix:

  - uses: git-checkout
    with:
      repository: https://github.com/luvit/luv
      tag: ${{vars.mangled-package-version}}  # Remove the "v" prefix
      expected-commit: 657a08fefcfe72bdabe90b63984c1b39dbcf75a4

• Explanation: The upstream repository luvit/luv uses tag formats without the "v" prefix. By removing the "v" prefix from the tag specification, the git checkout will be able to find and check out the correct version.

• Additional Notes:

• You can verify the correct tag format by checking the releases/tags page on the upstream repository
• The expected-commit hash appears correct, just the tag format needs adjustment
• This is a common pattern where some repos use "v" prefixes and others don't

• References:

• https://github.com/luvit/luv/releases (shows tag format)
• https://github.com/luvit/luv/tags