RCARS v1.5.10

Retirement status on every stage, and retirement Jiras under the epic

A retirement is started from one stage of a CI. Before, only that stage showed the retirement. Now every stage of the CI (.dev, .event, .prod) shows it.

New retirement Jira tickets now go under the retirement epic and start In Progress.

Retirement status on all stages

• Browse: sibling stages now show RETIREMENT RECOMMENDED or RETIRING <date>. Example: all LB2596 stages show RETIRING NOV 22, not only the stage the retirement was started from.
• This is a read-time join by stage family. It does not create or copy workflow rows. Workflows that are not approved yet are still ignored.

Catalog API

• GET /api/v1/catalog: each item has a new retirement_label field.
• GET /api/v1/catalog/{identifier}: now returns workflow_status, retirement_target_date, and retirement_label.
• retirement_label is recommended, in_progress, retired, or null.

Retirement Jira tickets

• New tickets get the retirement epic RHDPCD-2191 as parent. Tickets filed in another project (for example GPTEINFRA) get no parent.
• New tickets move to In Progress right after creation. If the transition fails, the start still succeeds, and the failure is logged.
• New setting RCARS_JIRA_RETIREMENT_PARENT (default RHDPCD-2191). Set it to empty to turn off the parent.
• Start Retirement now takes a lock per item. Two starts at the same time can no longer create two Jira tickets. The second start gets HTTP 409.

Deploy

• API only (--tags api). No reporting sync and no backfill are needed.

---

2 PRs · #186 · #187

Full diff: v1.5.9...v1.5.10

🤖 Generated with Claude Code