@fmeum you mentioned wanting a separate provider for binaries, do you have any preferences for names? And the provider is currently empty, I'm not sure what would make the most sense to put in that. Curious what you think!

ShInfo and ShBinaryInfo perhaps? They can be empty for now, but we can already replace allow_rules with them.

ShInfo and ShBinaryInfo perhaps? They can be empty for now, but we can already replace allow_rules with them.

Done!

(20:53:06) ERROR: /Users/buildkite/builds/bk-macos-intel-c3vz/bazel/rules-shell/tests/bcr/BUILD:12:10: in sh_binary rule //:bin:
/private/var/tmp/_bazel_buildkite/ee54915b9d2878a6f7884176de4ecfb4/external/rules_shell+/shell/private/sh_executable.bzl:29:5: rule advertised the 'ShInfo' provider, but this provider was not among those returned
(20:53:06) ERROR: /Users/buildkite/builds/bk-macos-intel-c3vz/bazel/rules-shell/tests/bcr/BUILD:12:10: Analysis of target '//:bin' (config: aaed0a7) failed
(20:53:06) ERROR: Analysis of target '//:bin' failed; build aborted

I think for backward compatibility we might need to leave allow_rules.

I think for backward compatibility we might need to leave allow_rules.

Disregard!

ShInfo and ShBinaryInfo perhaps? They can be empty for now, but we can already replace allow_rules with them.

Done!

I missed a spot, thakn you @fmeum !