Repository navigation
fix: preserve selected documentation traits - #2
Merged
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The website selects package traits for documentation, but SwiftPM 6.3.3 enables every trait when
dump-symbol-graphcreates its build plan. App Store Connect therefore rebuilt the full API after its selected build had already passed, expanding the documented surface and delaying deployment.Emit public symbol graphs and external extension blocks during the selected build, then convert the configured library modules. This keeps the published API surface consistent with
projects.jsonand removes the separate build of every trait and its test-runner workaround.Validation: all 27 pipeline tests pass. The new orchestration regression fails against the prior implementation and checks trait forwarding, one compilation, public and extension graphs, and library-only conversion. No local Swift or DocC compilation was repeated; the required Pages workflow validates the full hosted result. SwiftPM source.