Skip to content

RCARS v1.5.8

Choose a tag to compare

View all tags
@stencell stencell released this 23 Oct 08:31
· 19 commits to main since this release
v1.5.8
815558b
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Retire base components from Browse

Curators can now start the retirement workflow from Browse. This covers base components that sit under a published (virtual) CI. The Performance view merges their usage into the published CI and the Non-Prod view excludes them, so they had no retirement entry point before.

UI

  • Browse: curators and admins see a Retire button next to Edit on expanded lab cards. It opens the same retirement drawer as Performance and Non-Prod Items. Architecture cards do not get the button.
  • Retirement drawer: it now opens for items without performance data. It shows a "No performance data" note instead of the usage grid. The owner email omits the key metrics block when there are no metrics.
  • System → Recent Jobs: queued analyze jobs show their CI name. Running jobs are listed first, so a large queued backlog no longer hides them.

Scan efficiency

  • Sibling stages of one item (.dev, .event, .prod) that share a Showroom now queue behind one leader (prod preferred). The siblings reuse the leader's analysis instead of making their own LLM calls. On the first v1.5.7 prod rescan, 223 of 763 analyses could have been reused this way.
  • A per-source Postgres advisory lock holds siblings until the leader persists. The wait is capped at 300s, after which the scan proceeds and logs showroom_reuse_lock_timeout. Forced rescans (rescan-all) still skip reuse.
  • The leader-first ordering applies to the nightly Babylon pipeline, POST /analysis/scan, and rcars scan.

3 PRs · #179 · #180 · #183

Full diff: v1.5.7...v1.5.8

🤖 Generated with Claude Code

Assets 2
Loading