Luis Padron

I'll try to pick this up soon

@gferon I fixed the merge conflict. Did we want to merge this @keith @thii?

This would be great, along with `completion` we could really use this for `transform`. @natecook1000 is this something you think would be wanted? I could work on this if you...

This is probably related to the fact that `spm_parser` uses `1.2.0` version of `swift-argument-parser` ([here](https://github.com/cgrindel/rules_spm/blob/1b8626bcd863f19479f77d40cd09098681d38207/tools/spm_parser/Package.swift#L13)) and the parser gets run via `swift run` which fetches and rebuilds as needed. However,...

Looking at it a bit more, it seems like maybe caused by this change in Package.swift of swift-argument-parser: https://github.com/apple/swift-argument-parser/blob/main/Package%40swift-5.6.swift#L94-L108

Thanks! Wonder though what a solution here is that doesn't care about what version the internal tool is on?

Anyone able to add the signature tool to the existing `xcramework` rules? Happy to review / help with PRs that do that.

Can you be more specific?

The failures are due to DocC rules needing to be updated for rules_swift 2.0, thats being done over in: #2487 The intents tests are passing though via: ``` bazel test...

Just +1 that im seeing a similar issue: ``` 11:01:10 ERROR: Foo/BUILD.bazel:11:15: Compiling Foo.c failed: unable to finalize action: Missing digest: / for bazel-out/ios_arm64-opt-ios-arm64-min12.0-applebin_ios-ST-/bin/path/to/Foo.d ``` Our setup is a bit...