add lint for run_exports outside of a build section about conda-smithy HOT 5 OPEN

Both are fine, except when you have [...]

What's the benefit of allowing the build:-less way, except saving some characters? I don't think that's worth the footgun that comes along with it.

I mean, if we can lint the specific case that breaks, all the better, but I'd be equally happy to just require a build: section.

from conda-smithy.

The correct placement would be

outputs:
  - name: blah
    build:
      run_exports:
       - blah

from conda-smithy.

What's the benefit of allowing the build:-less way, except saving some characters? I don't think that's worth the footgun that comes along with it.

You'll shoot yourself in the foot if you only move run_exports to build and the other values are not moved to the build section.

from conda-smithy.

Both are fine, except when you have

outputs:
  - name: blah
    run_exports:
     - blah
     build:
       some_other_option: value

from conda-smithy.

Right. My proposal is to require only stuff under build in conda-forge to make things simpler and less error prone. We could lint exactly for the bug if we want OFC.

from conda-smithy.