MNT: rerender#8
Conversation
|
Hi! This is the friendly automated conda-forge-linting service. I failed to even lint the recipe, probably because of a conda-smithy bug 😢. This likely indicates a problem in your This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12170699425. Examine the logs at this URL for more detail. |
…onda-forge-pinning 2024.12.04.17.04.39
|
It appears that the linter is failing because the recipe file is named recipe.yaml instead of meta.yaml. Additionally, recipe.yaml contains a context: section, which does not seem to be valid syntax for meta.yaml. Is this intentional? Should we consider renaming it to meta.yaml and adjusting or removing the context section accordingly? |
|
Hmm, rerendering doesn't update the pytorch version (it still points to 2.4). Does anyone have an idea how to enforce this package to build with pytorch? I believe there are no actual blockers, just the migrator's error, which I'm not sure if it's fixed or actually broken though.. |
Ah, it's in recipe format for rattler-build: https://prefix-dev.github.io/rattler-build/latest/recipe_generation/ |
Hi! This is the friendly automated conda-forge-webservice.
I've started rerendering the recipe as instructed in #7.
If I find any needed changes to the recipe, I'll push them to this PR shortly. Thank you for waiting!
Here's a checklist to do before merging.
Fixes #7