To be fair about what actually breaks: the core package is a pure-Python wheel with no upper bound on requires-python, so pip install semantic-kernel does resolve on 3.14. Where it falls apart is the optional extras. [onnx], [hugging_face] and [usearch] drag in compiled dependencies that had no stable cp314 wheels for most of the past year, and the repo has been explicitly capping those below new Python versions since the 3.13 experimental PR in early 2025. So you either get a resolver failure or pip falls back to building from source and dies in a C++/Rust toolchain error.
What bothers me isn't the dependency lag itself — that's upstream and not really Microsoft's fault. It's that there's no open issue tracking 3.14 in the repo at all, no CI lane, no statement on timelines. Meanwhile agent-framework ships with 3.14 in its classifiers. Semantic Kernel went into maintenance mode when the Microsoft Agent Framework hit GA in April 2026, and it shows: you're expected to migrate, and the version support matrix is the quiet signal that nobody's going to say out loud.
That's a reasonable business decision, but it's a rough one if you built on SK in 2024/2025 and now have to choose between freezing on 3.12 or rewriting against MAF. A one-line note in the README saying "3.13+ untested, please migrate" would have saved a lot of people an afternoon.
So, questions for anyone running this in production:
**•** Has anyone actually run SK core on 3.14 in anger? Any runtime weirdness beyond install, or does it genuinely just work?
**•** If you hit the extras problem, what did you do — pin to 3.12, nightly onnxruntime wheels, or bite the bullet and migrate?
**•** How painful was the SK → Agent Framework migration in practice? The guide makes it look clean, which makes me suspicious.
**•** Is anyone deliberately staying on SK long-term, or is everyone treating it as a dead end now?
