Increment build number in meta.yaml

[anutosh491]

Checklist

• [x] Used a personal fork of the feedstock to propose changes
• [x] Bumped the build number (if the version is unchanged)
• [x] Reset the build number to 0 (if the version changed)
• [x] 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)
• [ ] Ensured the license file is being packaged.

[anutosh491]

@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/meta.yaml) and found some lint.

Here's what I've got...

For recipe/meta.yaml:

• This recipe is using a compiler, which now requires adding a build dependence on {{ stdlib("c") }} as well. Note that this rule applies to each output of the recipe using a compiler. For further details, please see https://github.com/conda-forge/conda-forge.github.io/issues/2102.

[anutosh491]

I see there was an update to 2.15.0 (https://github.com/conda-forge/fontconfig-feedstock/commit/97083a75cb09dfd7551ab128dc720a1fd7992738) but I only see 2.14.2 on conda-forge (https://anaconda.org/conda-forge/fontconfig)

I guess a simple build increment should fix this ? Or am I missing something ? @pkgw

[anutosh491]

@conda-forge-admin, please rerender

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

[anutosh491]

@jakirkham @ocefpaf @pkgw Could y'all let me know if this is the correct way to address this ?