Remove the breaking changes so the next release can be 2.1.0

[iziz]

Summary

Removes the two breaking changes that landed in #452, so the next release can be 2.1.0 instead of a major published days after 2.0.0.

Neither was required for Swift 6 adoption. All six statics that were errors in the Swift 6 language mode — the five facade shared instances and PhoneNumberFieldStyle.automatic — are fixed by purely additive Sendable conformances, which stay. The package still builds clean in the Swift 6 language mode with zero warnings.

Why not just number it 2.1.0 as-is

The podspecs depend on each other with ~> 2.0.1 and the README documents ~> 2.0. Shipping breaking changes as 2.1.0 means every consumer on ~> 2.0 picks them up on a routine update and finds out at compile time. The version number has to match the compatibility, so the fix is to remove the incompatibility.

What is reverted

PhoneNumberFieldState.error goes back to Error?. Narrowing it to PhoneNumberValueError made the state Sendable and its Equatable conformance synthesized, but it discarded information: callers previously received the NSError raised by the Objective-C core and could read its domain, code, and userInfo, where the enum preserves only a description string. The custom equality that compares error descriptions comes back with it.

PhoneNumberEnriching loses its Sendable requirement, along with the PhoneNumberFieldFormatter conformance it enabled. A protocol requirement added to a published protocol invalidates any conformance capturing non-Sendable state.

PhoneNumberFieldState is therefore not Sendable. Callers who need field state across a concurrency domain should derive a PhoneNumberValue, which is; the updated test demonstrates it and the changelog says so.

What is kept

Everything else from #452: the Swift 6 language mode, the tools-version bump, visionOS, all five facade Sendable conformances, PhoneNumberFieldStyle: Sendable, the PhoneNumberValueError improvements, the deprecation of PhoneNumberError, the test suites, the CI matrix, and the docs.

Remaining compatibility note

swift-tools-version:6.0 raises the minimum toolchain for Swift Package Manager consumers to Xcode 16. Deployment targets are unchanged and the CocoaPods specs accept Swift 5.9 or 6.0, so CocoaPods users are unaffected. This is documented at the top of the changelog's unreleased section rather than buried in a bullet.

Tests

• swift build — Swift 6 language mode, 0 warnings
• swift test — 231 XCTest + 43 Swift Testing, 0 failures
• git diff --check

Notes

• CHANGELOG.md is rewritten from "must be published as a major version" to a minor release, and the Sendable bullet now states which type is deliberately not Sendable and what to use instead.
• If you would rather keep the typed error and the Sendable protocol requirement, close this and release 3.0.0 instead. The trade is a stricter API against a major version bump one release after 2.0.0.

🤖 Generated with Claude Code