SwiftPackageIndex-Server: Package build failing due to sample code
Please describe the bug
We maintain a few nested projects in our swift-composable-architecture package, and they tend to always target the latest/greatest to demo new features. Recently, we added a macro dependency to one of these sample apps, but now the main build is failing, even though these targets are outside the main package:
https://swiftpackageindex.com/builds/136FD6AC-6A5C-486C-A3BB-5BA52D99533B
We do have an spi.yml specifying which schemes should be built, but I assume that even the presence of the other targets in the workspace are getting in the way.
Is there a way to specify just the project file and not the workspace in the spi.yml? Or is there another configuration option I’m not thinking of?
About this issue
- Original URL
- State: closed
- Created 6 months ago
- Comments: 19 (13 by maintainers)
That’s deployed and re-run:
That might be because I only tested with a similar command on my machine, not with the actual command that our builder uses. I’ll try this again with 1.5.5 and the actual build command tomorrow just to confirm that this used to work!
@finestructure Seems that bumping to 5.9 fixed a bunch! I’m a lil surprised by the visionOS failure, but think our Package.resolved file regressed. Hoping that’ll get fixed soon!