Swift 6 language mode enforces complete concurrency checking
Opt in per module. Sendable violations and cross-actor access that were warnings in Swift 5 mode become errors. This is the single largest source of migration work in a mature codebase, and it is deliberately opt-in per target so you can move one module at a time.
What to do
Enable complete concurrency checking in Swift 5 mode first and clear the warnings. Only then switch the module to Swift 6 mode.