Last week, the team released , and it is not just a minor patch—it changes how we think about configuration composition.
If you are on a legacy pipeline of 10,000+ lines of configs, pin your version to hydra-core==1.1.2 for now, but plan the migration. The deprecation of hydra.main means you will need to refactor your entry point logic. hydra 1.2
Version 1.2 introduces for certain resolver functions. Early benchmarks show a 40% reduction in instantiation time for large config suites. 5. Deprecation of hydra.main This is the breaking change you need to watch for. The decorator @hydra.main() has been a staple since day one. It now throws a DeprecationWarning . In Hydra 2.0 (planned for Q3 2026), it will be removed. Last week, the team released , and it
This change allows for better type checking and allows you to run Hydra inside Jupyter Notebooks (finally!) without weird hacks. Yes, but carefully. If you are starting a new project today, use Hydra 1.2 . The new composition rules and Jupyter support are worth it. Version 1