fix: ignore unresolved packages in Package.swift

[luispadron]

This fixes an issue where if a brand new dependency is added to the Package.swift when Package.resolved has not yet been updated, the Bazel build fails. It fails because there is no pin available for the source_control dependency as the Package.resolved has not yet been updated.

For example, a command line tool built using rules_swift_package_manager which has a Package.swift for swift-argument-parser. If a new dependency is added to the Package.swift but not yet used in any of the Bazel targets and no swift package resolve has been run when a build is run the build will fail with:

File bazel-path/external/rules_swift_package_manager~/swiftpkg/bzlmod/swift_deps.bzl", line 152, column 25, in _declare_pkg_from_dependency
                commit = pin.state.revision,
Error: 'NoneType' value has no field or method 'state'

This change allows the build to progress by simply ignoring the unresolved dependencies until a swift package resolve is run by the user.

[cgrindel]

Can you explain what the benefit is to the user? If I understand correctly, this would only be useful if you add a dep to Package.swift and not use it in your code.

[luispadron]

Can you explain what the benefit is to the user? If I understand correctly, this would only be useful if you add a dep to Package.swift and not use it in your code.

For us we need this because we have a CLI tool which uses the Package.swift to define deps. This CLI tool also has a command for working with the Package.swift, basically we automate updates for the Package.swift itself via the the CLI tool. As it is today, if I add a new dependency and then try to run our-cli package resolve it fails to build

[cgrindel]

Looks like we need to run bazel run //:tidy.

[cgrindel]

@Mergifyio queue

[mergify]

queue

✅ The pull request has been merged automatically

The pull request has been merged automatically at b81a341