Repository navigation
ci: Use diagnostics-action v0.0.1 - #511
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
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.
Use
philprime/diagnostics-action@v0.0.1for release environment diagnostics instead of embedding Xcode, SDK, and simulator inventories in the XCFramework build script. Run the action after the archive step withif: always()so diagnostics remain available on successful and failed builds.Retain Swift-version output and the package-only destination check. Version
v0.0.1requires a project or workspace for destination checks and cannot express TPPDF's scheme-only Swift package invocation. Archive creation and artifact publishing are unchanged.Verification
Workflow formatting,
actionlint, ShellCheck, and whitespace checks passed.make test-macosandmake lintalso passed. The XCFramework publishing workflow was not executed.