ART-19365: Extract and return pipeline status from releases.yml

[ashwindasr]

Summary

• Extract status field from each release entry in get_advisories()
• Pass status through get_branch_advisory_ids() as 4th element in the response
• Defaults to empty dict when no status field exists (backwards compatible)

Context

Companion to the art-tools PR that adds pipeline job completion status fields to releases.yml. The dashboard backend now extracts and forwards these fields to the frontend.

Test plan

• Test get_advisories() with mock YAML containing status -- verify extraction
• Test get_branch_advisory_ids() returns status as 4th element
• Test backwards compat with YAML missing status field -- should default to {}

Generated with Claude Code

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign jupierce for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@ashwindasr: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/security	f5ee3bf	link	false	/test security

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[openshift-ci-robot]

@ashwindasr: This pull request references ART-19365 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Summary

• Extract status field from each release entry in get_advisories()
• Pass status through get_branch_advisory_ids() as 4th element in the response
• Defaults to empty dict when no status field exists (backwards compatible)

Context

Companion to the art-tools PR that adds pipeline job completion status fields to releases.yml. The dashboard backend now extracts and forwards these fields to the frontend.

Test plan

• Test get_advisories() with mock YAML containing status -- verify extraction
• Test get_branch_advisory_ids() returns status as 4th element
• Test backwards compat with YAML missing status field -- should default to {}

Generated with Claude Code

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.