updated to version 0.15 which has multiple outputs

[phreed]

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.

This is a significant update as it produces additional output packages.

[phreed]

@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 top level meta keys are in an unexpected order. Expecting ['schema_version', 'context', 'recipe', 'source', 'build', 'outputs', 'about', 'extra'].

For recipe/recipe.yaml:

• ℹ️ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.
  • For the tests[].python.python_version or tests[].requirements.run section of hydra-kernel output, you should usually use the pin python_version: ${{ python_min }}.* or python ${{ python_min }}.* for the python_version or python entry.
  • For the tests[].python.python_version or tests[].requirements.run section of hydra-rdf output, you should usually use the pin python_version: ${{ python_min }}.* or python ${{ python_min }}.* for the python_version or python entry.
  • For the tests[].python.python_version or tests[].requirements.run section of hydra-pg output, you should usually use the pin python_version: ${{ python_min }}.* or python ${{ python_min }}.* for the python_version or python entry.
  • For the tests[].python.python_version or tests[].requirements.run section of hydra-ext output, you should usually use the pin python_version: ${{ python_min }}.* or python ${{ python_min }}.* for the python_version or python entry.
  • For the tests[].python.python_version or tests[].requirements.run section of hydra-python output, you should usually use the pin python_version: ${{ python_min }}.* or python ${{ python_min }}.* for the python_version or python entry.
  • If the package requires a newer Python version than the currently supported minimum version on conda-forge, you can override the python_min variable by adding a Jinja2 set statement at the top of your recipe (or using an equivalent context variable for v1 recipes).

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

[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/25177345637. 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.

[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:

• ℹ️ PyPI default URL is now pypi.org, and not pypi.io. You may want to update the default source url.
• ℹ️ PyPI default URL is now pypi.org, and not pypi.io. You may want to update the default source url.
• ℹ️ PyPI default URL is now pypi.org, and not pypi.io. You may want to update the default source url.
• ℹ️ PyPI default URL is now pypi.org, and not pypi.io. You may want to update the default source url.
• ℹ️ PyPI default URL is now pypi.org, and not pypi.io. You may want to update the default source url.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/25220306615. 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.

[phreed]

@conda-forge-admin, please rerender

This includes new packages: hydra-kernel, hydra-rdf, hydra-pg, while retaining hydra-python. It is expected that there will later be a hydra-ext.

[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:

• ℹ️ PyPI default URL is now pypi.org, and not pypi.io. You may want to update the default source url.
• ℹ️ PyPI default URL is now pypi.org, and not pypi.io. You may want to update the default source url.
• ℹ️ PyPI default URL is now pypi.org, and not pypi.io. You may want to update the default source url.
• ℹ️ PyPI default URL is now pypi.org, and not pypi.io. You may want to update the default source url.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/25228932929. 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.

[phreed]

This is similar to conda-forge/blpapi-feedstock#65 and the related discussion on https://conda-forge.zulipchat.com/#narrow/channel/457337-general/topic/Multi-output.20vs.20multi-feedstock/with/579057261

Hopefully, @beckermr can help me out.

[phreed]

@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/25454523577. Examine the logs at this URL for more detail.}

[phreed]

conda-forge/admin-requests#2060

Is a request to add the missing output packages.

[phreed]

@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/25499932854. Examine the logs at this URL for more detail.}

[phreed]

validation results:
  {
    "noarch/hydra-pg-0.15.0-pyh1ea3fb3_0.conda": false,
    "noarch/hydra-kernel-0.15.0-pyhc364b38_0.conda": false,
    "noarch/hydra-python-0.15.0-pyh8a8ef89_0.conda": true,
    "noarch/hydra-rdf-0.15.0-pyh8a8ef89_0.conda": false
  }
NOTE: Any outputs marked as False are not allowed for this feedstock. See https://conda-forge.org/docs/maintainer/infrastructure/#output-validation-and-feedstock-tokens for information on how to address this error.
Error: Process completed with exit code 1.

Do I need to wait longer or is there a defect in

• Create add-hydra-output.yml admin-requests#2060
• https://github.com/conda-forge/admin-requests/pull/2060/changes#diff-b03c22e70e7735a8d1aace4267f96fc97f98b56ce9ef5fc5ed4d4fa881ed5c5e