# Roadmap and breaking changes **URL:** \ **Category:** Get Help\ **Tags:** documentation, community-wg, ansible-lint\ **Created:** [January 18, 2026, 10:45pm UTC](https://forum.ansible.com/t/roadmap-and-breaking-changes/45127 "2026-01-18T22:45:12Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![juju4](https://avatars.discourse-cdn.com/v4/letter/j/dec6dc/32.png) [@juju4](https://forum.ansible.com/u/juju4)\ **Post date:** [January 25, 2026, 8:21pm UTC](https://forum.ansible.com/t/roadmap-and-breaking-changes/45127/5 "2026-01-25T20:21:49Z")
Thanks for the inputs. My definition of breaking change is that either now, either sooner or later, my code will break if left as is (including config). Deprecation warnings are indication of something that is planned to break at some point, I believe. I’m all for better quality, security, resiliency, performance and so on. My main goal is to keep track of those changes to anticipate them, ideally regroup them, so I and other users can avoid to do review all theirs roles, playbooks, variables and else too many times. imho, ideal target is once a year, two max, more than that for a volunteer contributor is too demanding. possibly too for work. I would think bug attached to deprecation are longer term issue usually with larger constraints than standard bug and that’s why they are not just patched/fixed immediately. I saw recently more deprecation warnings but unclear how to fix. - `[DEPRECATION WARNING]: Importing 'to_native' from 'ansible.module_utils._text' is deprecated. This feature will be removed from ansible-core version 2.24. Use ansible.module_utils.common.text.converters instead.` at top of playbook execution and `ansible -m setup`… Seen on [Deprecation warnings in ansible-core 2.20](https://forum.ansible.com/t/deprecation-warnings-in-ansible-core-2-20/44741) or [`ansible.posix.authorized_key` deprecation warning from import of to\_native · Issue #695 · ansible-collections/ansible.posix · GitHub](https://github.com/ansible-collections/ansible.posix/issues/695) - `The internal "vars" dictionary is deprecated.` Also [The internal "vars" dictionary is deprecated · Issue #86434 · ansible/ansible · GitHub](https://github.com/ansible/ansible/issues/86434) - `[DEPRECATION WARNING]: Importing '_AnsibleActionDone' is deprecated.` I believe that those like above are more in ansible-core. not asking to duplicate. Some instructions to locate deprecated code and how to fix it would be really helpful. Like linters do [args - Ansible Lint Documentation](https://docs.ansible.com/projects/lint/rules/args/#special-cases) And ideally deprecation is included in linter early on, first as warning (before or when deprecation warning added), and next error (before full deprecation). --- _[View the full topic](https://forum.ansible.com/t/roadmap-and-breaking-changes/45127)._