Do you still use bzlmod or legacy WORKSPACE to load your external dependencies?

[cgrindel]

With the merge of #957, the support for Bazel projects that use legacy WORKSPACE has degraded and may be broken. Fixing this regression is possible, but it is not trivial. At a minimum, we would need to update the original legacy tests to work properly. However, the bigger issue is that the update-repos Gazelle action no longer exists. So, rules_swift_package_manager has no way to generate the swift_deps.bzl. A new tool would need to be written to generate the file.

To determine a path forward, I would like to hear from everyone that uses rules_swift_package_manager on how they load their Bazel external dependencies.

[cgrindel]

After reviewing the poll results and evaluating the work needed to continue to support legacy workspaces, we have opted to not support legacy workspaces, directly. Instead, we recommend that clients that use legacy workspaces use Bazel's hybrid mode.