uv-build 0.7.2 (rattler-build, abi3, shellcheck)

[bollwyvl]

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

References:

• includes uv-build v0.6.17 #4
• includes uv-build v0.7.0 #6
• includes uv-build v0.7.2 #8

Changes:

• use rattler-build
• use abi3 (as per upstream, pip check against python_min and 3.13)
• use pixi (was getting segfaults with the default?)
• use shellcheck

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/recipe.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe/recipe.yaml:

• ℹ️ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/14764345651. Examine the logs at this URL for more detail.}

[bollwyvl]

@conda-forge/uv-build ready for review!

[bollwyvl]

@conda-forge/uv-build back to ready for review with 0.7.1

[isuruf]

We should get prefix-dev/rattler-build#1592 fixed ASAP

[bollwyvl]

cool: is there anything to be done here?

[isuruf]

This should be under a is_abi3 check

[bollwyvl]

@conda-forge-admin please rerender

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/14760185341. Examine the logs at this URL for more detail.}

[isuruf]

This needs to be within a is_abi3 block too

[bollwyvl]

trying ${{ is_abi3 }}: didn't seem like the schema likes if in that block?

[bollwyvl]

@conda-forge-admin please rerender

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipe/recipe.yaml) and found some lint.

Here's what I've got...

For recipe/recipe.yaml:

• ❌ The is_abi3 variant variable is now a boolean value instead of a string (i.e., 'true' or 'false'). Please change syntax like is_abi3 == 'true' to is_abi3`.

For recipe/recipe.yaml:

• ℹ️ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/14796804621. Examine the logs at this URL for more detail.}

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/recipe.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe/recipe.yaml:

• ℹ️ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/14796817689. Examine the logs at this URL for more detail.}