1.7.0

What's Changed

Important

This release contains a bug fix (#171) that may introduce new fatal errors or test failures to your test suite. Previous versions of Issue Reporting were swallowing test failures reported outside of a Swift Testing test's task. This release of Issue Reporting addresses this issue by always reporting issues to Swift Testing, regardless of current test task. In Swift <6.2, this results in a fatal error (the same behavior as Swift Testing when #expect or Issue.record is called outside a test's task). In Swift >=6.2, this results in a test failure that isn't attributed to a specific test (also matching the latest behavior in Swift Testing).

• Added: Overloads to withErrorReporting to prevent returning double-nested optionals from the operation (thanks @natemann, #168).
• Fixed: Always invoke Issue.record and XCTFail in tests to surface out-of-band Swift Testing failures (#171).

New Contributors

• @natemann made their first contribution in #168

Full Changelog: 1.6.1...1.7.0