Yannik Tausch

> In light of #1893 please update your answer. I don't see how #1893 changes the situation. The bot uses the entirety of conda-forge.yml, not only the bot section. My...

xref #463 #535

I signed the CLA.

@conda-bot check

> Where in the current meta.yaml we should define the PURLs. about seems to be the most obvious one, which means this will probably end up in info/about.json. I agree...

> include purls as an alternative package identifier I don't follow entirely. What would your example refer to? The PyPI package or the corresponding conda-forge package?

@beckermr What do you mean by "expanding the ruleset"? My PR already contains more rulesets than the default (and more than you propose): https://github.com/conda-forge/conda-smithy/blob/12f4a1fa107b75069d5380e166b2d5d41cbb6ed9/pyproject.toml#L36-L52 Also, what is the rationale behind...

Note: The signature of `lintify_forge_yaml` changed but makes a lot more sense now since not all lints or hints must be JSON validation-related. Formally, this would require a deprecation process...

What is the status of this PR? @conda-forge/core @isuruf

@isuruf