Skip to content

[6.2] Promote Issue Handling Traits to public API #1228

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

stmontgomery
Copy link
Contributor

  • Explanation: This PR promotes issue handling traits (namely, the IssueHandlingTrait type) to non-@_spi public API, now that it has been accepted by the Testing Workgroup.
  • Scope: New trait API.
  • Issues: rdar://150057037
  • Original PRs: Promote Issue Handling Traits to public API #1198
  • Risk: Low
  • Testing: New unit tests included
  • Reviewers: @briancroom

@stmontgomery stmontgomery added this to the Swift 6.2 milestone Jul 17, 2025
@stmontgomery stmontgomery self-assigned this Jul 17, 2025
@stmontgomery stmontgomery added documentation 📚 Improvements or additions to documentation enhancement New feature or request public-api Affects public API issue-handling Related to Issue handling within the testing library traits Issues and PRs related to the trait subsystem or built-in traits integration ⚙️ Integrating work to release branches labels Jul 17, 2025
@stmontgomery
Copy link
Contributor Author

@swift-ci please test

@stmontgomery stmontgomery merged commit 9d0323e into swiftlang:release/6.2 Jul 17, 2025
3 checks passed
@stmontgomery stmontgomery deleted the publicize-issue-handling-traits-6.2 branch July 17, 2025 12:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation 📚 Improvements or additions to documentation enhancement New feature or request integration ⚙️ Integrating work to release branches issue-handling Related to Issue handling within the testing library public-api Affects public API traits Issues and PRs related to the trait subsystem or built-in traits
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants