RC version of PR 203

[mrclary]

See #203.

1. Release 6.0.4rc1 to PyPi
2. Update feedstock in this PR:
   • version: 6.0.4rc1
   • build: 0
   • sha256: from PyPi
3. Verify checks succeed
4. Merge this PR
5. Proceed with 6.0.4rc1 release to conda-forge and GitHub

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

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

For recipe/meta.yaml:

• ℹ️ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.
  • For the host section of <output 1 output, you should usually use python {{ python_min }} for the python entry.
  • For the run section of <output 1 output, you should usually use python >={{ python_min }} for the python entry.
  • For the test.requires section of <output 1 output, you should usually use python {{ python_min }} for the 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).
• ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). This parser is not currently used by conda-forge, but may be in the future. We are collecting information to see which recipes are compatible with grayskull.

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

[dalthviz]

@conda-forge-admin, please rerender