)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"0413c04d2370dbdadccb379ca60b2e9bb4c185ff","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"315d529e_f29698ac","updated":"2025-06-10 09:38:08.000000000","message":"@cardoe@cardoe.com You\u0027ll need to submit a patch to OSC _ignoring_ these new fields, then add a depends-on on that patch here, cut a release of SDK, and finally add a new patch to OSC re-adding the patch and bumping the minimum SDK to the new release. Sorry, it\u0027s a bit of a dance but that\u0027s the downside of having an automatic extraction of fields combined with manual tests.\n\nAlternatively, if you want to rework the OSC tests so that they use a subset check (the results include at least these fields), that would avoid the dance albeit at a small cost of test comprehensiveness.","commit_id":"919ce50ba49b3aad4771c24b134a7f50687b8907"},{"author":{"_account_id":5890,"name":"Doug Goldstein","email":"cardoe@cardoe.com","username":"cardoe"},"change_message_id":"b5b86464cae99446052127ce7894559bd7156a26","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":2,"id":"4d1fb148_721da9e0","updated":"2025-10-27 16:30:44.000000000","message":"@stephenfin@redhat.com can you confirm that https://review.opendev.org/c/openstack/python-openstackclient/+/963947 is what you believe is the appropriate way?","commit_id":"7e1eacaf825ce926b022d268aeb2863059b308a8"}]}
