)]}'
{"doc/source/contributor/concurrency.rst":[{"robot_id":"zuul","robot_run_id":"c681f7ff986944d491f6c07c4968eb3e","url":"https://zuul.teim.app/t/main/buildset/c681f7ff986944d491f6c07c4968eb3e","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":"a7d32f76c22185fa11e0b021c9badc1bcc1d886c","patch_set":1,"id":"b295c907_f51aec18","line":255,"updated":"2026-02-19 17:06:24.000000000","message":"Documentation warning placement could be more prominent in concurrency.rst\n\n**Severity**: WARNING | **Confidence**: 0.8\n\n**Impact**: The deprecation warning is placed after the technical explanation of taskflow\u0027s revert behavior. Users reading about revert functionality may see the technical details before seeing the deprecation notice.\n\n**Suggestion**:\nConsider moving the warning directive to appear immediately after the first mention of revert/rollback functionality in the document, or add a cross-reference to the warning when revert behavior is first described.","commit_id":"a9b90ca0036816c2a97f6283d363fa3bbcf39439"}],"releasenotes/notes/deprecate_actionplan_rollback_opt-9447a2b26bbe476e.yaml":[{"robot_id":"zuul","robot_run_id":"54214e348525454d87de928bc502a29a","url":"https://zuul.teim.app/t/main/buildset/54214e348525454d87de928bc502a29a","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":"009c8663c0d7189a75f039610fb93b7d57ff17ae","patch_set":1,"id":"1f4e66fc_27544d2f","line":1,"updated":"2026-02-19 14:34:38.000000000","message":"Consider adding upgrade impact notes for users who may have this configuration option set\n\n**Severity**: SUGGESTION | **Confidence**: 0.7\n\n**Benefit**: Users with rollback_when_actionplan_failed\u003dTrue in their configuration should understand that this setting will be ignored in future releases. Upgrade notes help with migration planning.\n\n**Recommendation**:\nExpand the release note to include an \u0027upgrade\u0027 section noting that users with this option enabled can safely remove it from their configuration, as the rollback functionality is not working anyway.","commit_id":"a9b90ca0036816c2a97f6283d363fa3bbcf39439"},{"robot_id":"zuul","robot_run_id":"6dd89389c0b54838bc140ffcf083b2e2","url":"https://zuul.teim.app/t/main/buildset/6dd89389c0b54838bc140ffcf083b2e2","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":"f95e2b8961499cdb63a66493b1fb32467cda959a","patch_set":1,"id":"5962e80c_7d33e130","line":1,"updated":"2026-02-06 15:34:47.000000000","message":"Consider clarifying the deprecation version in the release note\n\n**Severity**: SUGGESTION | **Confidence**: 0.7\n\n**Benefit**: Would provide users with clearer timeline for when this feature will be completely removed, helping them plan migration\n\n**Recommendation**:\nConsider adding a specific removal cycle (e.g., \u00272027.1\u0027) to the release note to match the deprecated_since\u003d\u00272026.1\u0027 setting. However, since this is a non-functional feature being deprecated, the current approach of not specifying exact removal is acceptable.","commit_id":"a9b90ca0036816c2a97f6283d363fa3bbcf39439"},{"robot_id":"zuul","robot_run_id":"c681f7ff986944d491f6c07c4968eb3e","url":"https://zuul.teim.app/t/main/buildset/c681f7ff986944d491f6c07c4968eb3e","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":"a7d32f76c22185fa11e0b021c9badc1bcc1d886c","patch_set":1,"id":"a792b5e4_96104c80","line":1,"updated":"2026-02-19 17:06:24.000000000","message":"Release note could include version when the deprecated option will be removed\n\n**Severity**: SUGGESTION | **Confidence**: 0.8\n\n**Benefit**: Adding a planned removal version (e.g., \u00272027.1\u0027 or specific future release) helps operators plan their migration and understand the timeline for removing this configuration option.\n\n**Recommendation**:\nConsider adding a sentence like \u0027This option is planned for removal in the 2027.1 release.\u0027 to provide users with a clear timeline for the removal.","commit_id":"a9b90ca0036816c2a97f6283d363fa3bbcf39439"},{"robot_id":"zuul","robot_run_id":"54214e348525454d87de928bc502a29a","url":"https://zuul.teim.app/t/main/buildset/54214e348525454d87de928bc502a29a","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":"009c8663c0d7189a75f039610fb93b7d57ff17ae","patch_set":1,"id":"00b9cfb8_ed58ff7c","line":1,"updated":"2026-02-19 14:34:38.000000000","message":"Release note filename does not follow standard reno naming convention - uses full option name instead of a brief identifier\n\n**Severity**: WARNING | **Confidence**: 0.8\n\n**Impact**: While the file is functional, the naming pattern \u0027deprecate_actionplan_rollback_opt\u0027 is unusually long. Standard reno naming typically uses shorter, descriptive identifiers.\n\n**Suggestion**:\nConsider using a shorter, more conventional release note filename like \u0027deprecate-rollback-9447a2b26bbe476e.yaml\u0027 or similar pattern. However, the current filename is acceptable as it\u0027s descriptive.","commit_id":"a9b90ca0036816c2a97f6283d363fa3bbcf39439"}],"watcher/conf/applier.py":[{"robot_id":"zuul","robot_run_id":"d828e29529f446558770f1d45421997c","url":"https://zuul.teim.app/t/main/buildset/d828e29529f446558770f1d45421997c","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":"883047d7d3d37c61ed794e12b0c931ce3811f841","patch_set":1,"id":"d4a1216c_9e9c272b","line":1,"updated":"2026-02-19 20:55:08.000000000","message":"Typo in commit message: \u0027configuraton\u0027 instead of \u0027configuration\u0027\n\n**Severity**: WARNING | **Confidence**: 1.0\n\n**Impact**: Minor documentation issue that does not affect code functionality\n\n**Suggestion**:\nFix the typo in future commits. Consider amending if this hasn\u0027t been pushed yet, though it\u0027s minor enough to not block merge.","commit_id":"a9b90ca0036816c2a97f6283d363fa3bbcf39439"},{"robot_id":"zuul","robot_run_id":"54214e348525454d87de928bc502a29a","url":"https://zuul.teim.app/t/main/buildset/54214e348525454d87de928bc502a29a","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":"009c8663c0d7189a75f039610fb93b7d57ff17ae","patch_set":1,"id":"1e096bc4_6bf2b78e","line":46,"updated":"2026-02-19 14:34:38.000000000","message":"Consider adding a FutureImport note or TODO comment for when to remove the deprecated option\n\n**Severity**: SUGGESTION | **Confidence**: 0.7\n\n**Benefit**: Adding a target release version (e.g., \u0027remove in 2027.1\u0027) helps with release planning and ensures the option is actually removed in a future release.\n\n**Recommendation**:\nUpdate the deprecated_since or deprecated_reason to include a target release for removal, e.g., deprecated_reason\u003d\u0027This feature does not work. Will be removed in the 2027.1 release.\u0027","commit_id":"a9b90ca0036816c2a97f6283d363fa3bbcf39439"},{"robot_id":"zuul","robot_run_id":"c681f7ff986944d491f6c07c4968eb3e","url":"https://zuul.teim.app/t/main/buildset/c681f7ff986944d491f6c07c4968eb3e","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":"a7d32f76c22185fa11e0b021c9badc1bcc1d886c","patch_set":1,"id":"3391fce6_4fb04311","line":52,"updated":"2026-02-19 17:06:24.000000000","message":"Line length exceeds the configured 79-character limit in configuration help text\n\n**Severity**: WARNING | **Confidence**: 0.9\n\n**Impact**: The help text for deprecated_reason spans multiple lines and exceeds the project\u0027s line length limit of 79 characters as configured in pyproject.toml. While ruff may handle this, consistency with project standards is important.\n\n**Suggestion**:\nConsider splitting the deprecated_reason text into multiple string literals or using implicit string concatenation to keep each line under 79 characters. Alternatively, verify that ruff pre-commit hooks properly handle this case.","commit_id":"a9b90ca0036816c2a97f6283d363fa3bbcf39439"}]}