)]}'
{"doc/source/integrations/index.rst":[{"robot_id":"zuul","robot_run_id":"21393f9df1a94325aedd5acfcb65e8fd","url":"https://zuul.teim.app/t/main/buildset/21393f9df1a94325aedd5acfcb65e8fd","author":{"_account_id":28006,"name":"teim-ci","display_name":"teim-ci","email":"ci@seanmooney.info","username":"ci-sean-mooney","status":"this is a third-party ci account run by sean-k-mooney on irc\nhosted at zuul.teim.app"},"tag":"autogenerated:zuul:automatic-ci","change_message_id":"136a5d03283834104665ed7b17d167615cd0af1e","patch_set":2,"id":"ea497941_9a43664d","line":98,"updated":"2026-02-06 15:41:43.000000000","message":"The documentation update could reference the specific release note for additional details.\n\n**Severity**: SUGGESTION | **Confidence**: 0.7\n\n**Benefit**: Improves documentation cross-referencing and helps users find detailed information about the deprecation.\n\n**Recommendation**:\nConsider adding a \u0027.. seealso::\u0027 or \u0027.. note::\u0027 directive referencing the release note section or providing a link to upgrade notes when they become available.","commit_id":"201fda5f5d6d27a647a3902b87f718d92cbe9ab0"}],"releasenotes/notes/deprecate-maas-9dfbb7975d379231.yaml":[{"robot_id":"zuul","robot_run_id":"21393f9df1a94325aedd5acfcb65e8fd","url":"https://zuul.teim.app/t/main/buildset/21393f9df1a94325aedd5acfcb65e8fd","author":{"_account_id":28006,"name":"teim-ci","display_name":"teim-ci","email":"ci@seanmooney.info","username":"ci-sean-mooney","status":"this is a third-party ci account run by sean-k-mooney on irc\nhosted at zuul.teim.app"},"tag":"autogenerated:zuul:automatic-ci","change_message_id":"136a5d03283834104665ed7b17d167615cd0af1e","patch_set":2,"id":"ba0685d5_7de1d5f8","line":1,"updated":"2026-02-06 15:41:43.000000000","message":"The release note could benefit from a more explicit migration path or recommendation for users who may be using MAAS integration.\n\n**Severity**: SUGGESTION | **Confidence**: 0.7\n\n**Benefit**: Provides clearer guidance to users who may be affected by this deprecation, improving user experience during transition.\n\n**Recommendation**:\nConsider adding a sentence like \u0027Users of the MAAS integration should provide feedback to the Watcher team if this feature is important to their deployment, or plan to migrate to alternative solutions.\u0027","commit_id":"201fda5f5d6d27a647a3902b87f718d92cbe9ab0"}],"watcher/common/clients.py":[{"robot_id":"zuul","robot_run_id":"92af20bcf9954536b40ec77843146b4c","url":"https://zuul.teim.app/t/main/buildset/92af20bcf9954536b40ec77843146b4c","author":{"_account_id":28006,"name":"teim-ci","display_name":"teim-ci","email":"ci@seanmooney.info","username":"ci-sean-mooney","status":"this is a third-party ci account run by sean-k-mooney on irc\nhosted at zuul.teim.app"},"tag":"autogenerated:zuul:automatic-ci","change_message_id":"1b747129d9799ad6e05bb2116b99e63c58271991","patch_set":1,"id":"db4c61ba_27c5020b","line":241,"updated":"2026-01-22 11:28:47.000000000","message":"Consider adding a roadmap or timeline for MAAS integration removal\n\n**Severity**: SUGGESTION | **Confidence**: 0.7\n\n**Benefit**: Would provide users with clearer expectations about when the integration will be removed and help them plan migration strategies\n\n**Recommendation**:\nAdd a comment or documentation reference indicating the target release version for complete removal, such as \u0027to be removed in the 2026.2 release\u0027","commit_id":"2f52c66581b5bd3c35f0204609ff9985fa5902da"},{"robot_id":"zuul","robot_run_id":"92af20bcf9954536b40ec77843146b4c","url":"https://zuul.teim.app/t/main/buildset/92af20bcf9954536b40ec77843146b4c","author":{"_account_id":28006,"name":"teim-ci","display_name":"teim-ci","email":"ci@seanmooney.info","username":"ci-sean-mooney","status":"this is a third-party ci account run by sean-k-mooney on irc\nhosted at zuul.teim.app"},"tag":"autogenerated:zuul:automatic-ci","change_message_id":"1b747129d9799ad6e05bb2116b99e63c58271991","patch_set":1,"id":"df2d2949_84f738a9","line":243,"updated":"2026-01-22 11:28:47.000000000","message":"Missing DeprecationWarning import in clients.py\n\n**Severity**: WARNING | **Confidence**: 0.8\n\n**Impact**: The deprecation warning references DeprecationWarning but it\u0027s not imported, which could cause a NameError when the method is called\n\n**Suggestion**:\nAdd \u0027from warnings import DeprecationWarning\u0027 or \u0027DeprecationWarning \u003d warnings.DeprecationWarning\u0027 to properly reference the warning class","commit_id":"2f52c66581b5bd3c35f0204609ff9985fa5902da"},{"robot_id":"zuul","robot_run_id":"21393f9df1a94325aedd5acfcb65e8fd","url":"https://zuul.teim.app/t/main/buildset/21393f9df1a94325aedd5acfcb65e8fd","author":{"_account_id":28006,"name":"teim-ci","display_name":"teim-ci","email":"ci@seanmooney.info","username":"ci-sean-mooney","status":"this is a third-party ci account run by sean-k-mooney on irc\nhosted at zuul.teim.app"},"tag":"autogenerated:zuul:automatic-ci","change_message_id":"136a5d03283834104665ed7b17d167615cd0af1e","patch_set":2,"id":"5a1c3573_4bd3a868","line":242,"updated":"2026-02-06 15:41:43.000000000","message":"Line 242 exceeds 79-character limit (line-length \u003d 79 configured in pyproject.toml). The line is 88 characters long.\n\n**Severity**: WARNING | **Confidence**: 0.9\n\n**Impact**: Violates project\u0027s configured line length standard. Will fail ruff linting checks (E501).\n\n**Suggestion**:\nBreak the deprecation message string across multiple lines or shorten the message to fit within 79 characters. For example: debtcollector.deprecate(\u0027MAAS integration is deprecated and will be removed in a future release.\u0027, version\u003d\u00272026.1\u0027, category\u003dDeprecationWarning)","commit_id":"201fda5f5d6d27a647a3902b87f718d92cbe9ab0"},{"robot_id":"zuul","robot_run_id":"21393f9df1a94325aedd5acfcb65e8fd","url":"https://zuul.teim.app/t/main/buildset/21393f9df1a94325aedd5acfcb65e8fd","author":{"_account_id":28006,"name":"teim-ci","display_name":"teim-ci","email":"ci@seanmooney.info","username":"ci-sean-mooney","status":"this is a third-party ci account run by sean-k-mooney on irc\nhosted at zuul.teim.app"},"tag":"autogenerated:zuul:automatic-ci","change_message_id":"136a5d03283834104665ed7b17d167615cd0af1e","patch_set":2,"id":"c6841107_63035b9d","line":243,"updated":"2026-02-06 15:41:43.000000000","message":"The deprecation category changed from PendingDeprecationWarning to DeprecationWarning. This is a more aggressive deprecation signal that will produce visible warnings to users.\n\n**Severity**: WARNING | **Confidence**: 0.8\n\n**Impact**: Users will immediately see DeprecationWarnings when using MAAS integration. This may break deployments that treat warnings as errors. Consider whether this is the intended behavior for an experimental feature.\n\n**Suggestion**:\nConsider if PendingDeprecationWarning is more appropriate initially, giving users one release cycle before switching to DeprecationWarning. Alternatively, document this breaking change clearly in the release notes.","commit_id":"201fda5f5d6d27a647a3902b87f718d92cbe9ab0"},{"robot_id":"zuul","robot_run_id":"21393f9df1a94325aedd5acfcb65e8fd","url":"https://zuul.teim.app/t/main/buildset/21393f9df1a94325aedd5acfcb65e8fd","author":{"_account_id":28006,"name":"teim-ci","display_name":"teim-ci","email":"ci@seanmooney.info","username":"ci-sean-mooney","status":"this is a third-party ci account run by sean-k-mooney on irc\nhosted at zuul.teim.app"},"tag":"autogenerated:zuul:automatic-ci","change_message_id":"136a5d03283834104665ed7b17d167615cd0af1e","patch_set":2,"id":"9f871ab7_00607528","line":243,"updated":"2026-02-06 15:41:43.000000000","message":"The deprecation version \u00272026.1\u0027 appears premature. Current development is on master for the 2025.2 release cycle (based on stable branches: 2024.2, 2025.1, 2025.2). Using 2026.1 suggests removal in a release that is two cycles away.\n\n**Severity**: WARNING | **Confidence**: 0.8\n\n**Impact**: Confusing version numbering that may not align with OpenStack release cycle. Deprecation typically targets the next release (2025.2 or 2026.1 at most one cycle out).\n\n**Suggestion**:\nVerify the intended release cycle and adjust version accordingly. If deprecation is for 2025.2 release, use \u00272025.2\u0027. If planning removal later, consider \u00272026.1\u0027 but document the multi-cycle deprecation plan. The commit is on master which targets 2025.2, so version\u003d\u00272025.2\u0027 may be more appropriate for deprecation warning.","commit_id":"201fda5f5d6d27a647a3902b87f718d92cbe9ab0"}]}