Fix meta.yaml logic for autotick-bot compatibility

traversaro commented 3 years ago

This PR changes the definition of the version variable to match the format used in the tags, i.e. 4_4.1.0, so that the autotick-bot (that extracts the version information from git tags by stripping all the characters till the first digit) works fine. The version in 4.1.0 format is now contained in the version_package variable (see https://github.com/conda-forge/libignition-msgs1-feedstock/issues/50 and https://github.com/conda-forge/libignition-msgs1-feedstock/issues/53 ).

Checklist

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

conda-forge-linter commented 3 years ago

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.

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

For recipe:

Jinja2 variable references are suggested to take a {{<one space><variable name><one space>}} form. See lines [57].

traversaro commented 3 years ago

@conda-forge-admin, please rerender

conda-forge-linter commented 3 years ago

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.

conda-forge / libignition-rendering4-feedstock