BUG: MACOSX_SDK_VERSION not participating in merge logic (original) (raw)

I just noticed that is a recipe uses

c_stdlib_version:          # [osx and x86_64]
  - "10.12"                # [osx and x86_64]
MACOSX_SDK_VERSION:        # [osx and x86_64]
  - "10.12"                # [osx and x86_64]

the merge logic of smithy will not be applied to MACOSX_SDK_VERSION, which will end up being incorrectly populated as 10.12 (while MACOSX_DEPLOYMENT_TARGET ends up being 10.13 after the merge with the global pinning).

I guess we should also add a linter warning for c_stdlib_version / MACOSX_SDK_VERSION <10.13?

CC @beckermr