)]}'
{"releasenotes/notes/remove-wsgi-scripts-entry-point-4e4eeec78e174a07.yaml":[{"robot_id":"zuul","robot_run_id":"686e2a7314ef4407a9201b96f683f03a","url":"https://zuul.teim.app/t/main/buildset/686e2a7314ef4407a9201b96f683f03a","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":"f240dea76f45b843ff18bdb22c0d0a467dda431d","patch_set":1,"id":"98094994_b3a9373d","line":8,"updated":"2026-02-24 22:00:56.000000000","message":"Release note references \u0027cyborg.wsgi.api:application\u0027 but could be more explicit about how to use it in practice\n\n**Severity**: WARNING | **Confidence**: 0.8\n\n**Impact**: While technically correct, the release note could be clearer about the exact uwsgi configuration needed since the module exports \u0027application\u0027 as a module-level variable, not a callable entry point\n\n**Suggestion**:\nConsider clarifying in the release note that deployers should use \u0027module \u003d cyborg.wsgi.api:application\u0027 for uwsgi configuration or provide explicit configuration examples showing both the old and new setup patterns.","commit_id":"854f04913802cecc925748fd78d9be2c8de6c1a4"}]}