Fix SPI build: add SPI_GENERATE_DOCS=1 flag to enable swift-docc-plugin #273
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
karulont
approved these changes
Jan 22, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Our SPI builds have been failing on
main, probably due to removing Swift Docc plugin by default: #240.The roots cause is SPI has a grep for
"https://github.com/swiftlang/swift-docc-plugin", as noted in SwiftPackageIndex/SwiftPackageIndex-Server#3061 (comment).The grep isn't smart enough to realize our
swift-docc-plugindep is gated behind a opt-in flag, so SPI doesn't add in theswift-docc-plugin.The recommendation seems to be to use the
SPI_GENERATE_DOCS=1flag (e.g. SwiftPackageIndex/SwiftPackageIndex-Server#3061 (comment))So hopefully this fixes the SPI build issues.