Skip to content

Add documentation for the Soundness API breakage check - #325

Open
bkhouri wants to merge 1 commit into
bkhouri/main/soudness_api_diff_support_additional_tool_argsfrom
bkhouri/main/soundness-api-diff-add-docs
Open

bkhouri wants to merge 1 commit into
bkhouri/main/soudness_api_diff_support_additional_tool_argsfrom
bkhouri/main/soundness-api-diff-add-docs

Conversation

@bkhouri

@bkhouri bkhouri commented Oct 16, 2026 •

Copy link
Copy Markdown
Collaborator

Add docs/soundness-api-breakage-check.md describing the api-breakage-check job in the Soundness workflow, alongside the existing docs-check documentation.

The document covers:

  • How the job works: checkout settings, baseline selection (explicit baseline or the PR base branch), and how the allowlist and additional tool arguments are passed to swift package diagnose-api-breaking-changes
  • Requirements, including the need for a pull_request trigger unless api_breakage_check_baseline is set
  • A reference table of the api_breakage_check_* inputs
  • Common scenarios: release-tag baseline, allowlist, additional tool arguments, custom container image, and disabling the check
  • Troubleshooting for common failures

Add docs/soundness-api-breakage-check.md describing the
`api-breakage-check` job in the Soundness workflow, alongside the
existing docs-check documentation.

The document covers:
- How the job works: checkout settings, baseline selection (explicit
  baseline or the PR base branch), and how the allowlist and additional
  tool arguments are passed to `swift package diagnose-api-breaking-changes`
- Requirements, including the need for a `pull_request` trigger unless
  `api_breakage_check_baseline` is set
- A reference table of the `api_breakage_check_*` inputs
- Common scenarios: release-tag baseline, allowlist, additional tool
  arguments, custom container image, and disabling the check
- Troubleshooting for common failures
@bkhouri
bkhouri requested a review from a team as a code owner October 16, 2026 06:21
@bkhouri
bkhouri added this pull request to stack #326 October 16, 2026 06:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants