Use build instead of number as variable for build number

[traversaro]

I noticed that recent rebuild were not bumping the build number, see for example:

• https://github.com/conda-forge/jaxlib-feedstock/pull/244
• https://github.com/conda-forge/jaxlib-feedstock/pull/234
• https://github.com/conda-forge/jaxlib-feedstock/pull/231

I looked into this, and apparently the bot assumes that the variable used to set the build number needs to be called either build or build_number, but not number as done in this recipe, see https://github.com/regro/cf-scripts/blob/bc57282361ba7437a46ee7ddde0783b94f1c1bc8/conda_forge_tick/update_recipe/build_number.py#L5-L11 .

I choose to use build as it is the variable name more used in conda-forge and used in the knowledge base: https://github.com/conda-forge/conda-forge.github.io/blob/26db656d1b1828b14fa24f16820ba30ec31c387f/docs/maintainer/knowledge_base.md#L968 .

Checklist

• [x] 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 code>@<space/conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• [x] Ensured the license file is being packaged.

[conda-forge-webservices[bot]]

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) and found it was in an excellent condition.

[traversaro]

I did not re-rendered or bumped the build number as this change does not change the generated recipe.

[xhochy]

Done in https://github.com/conda-forge/jaxlib-feedstock/pull/250

[traversaro]

Done in #250

Perfect, thanks!