RAC v0.8.11 - the "why it matters" release #65
tcballard
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
The "why it matters" release - every finding RAC reports now carries the reason it matters, in every place you might read it. And new users get their editor sorted in the first minute.
pip install --upgrade 'requirements-as-code[explorer]' rac explorerEvery finding explains itself, everywhere
Explorer's recommendations have always told you why a finding matters - "a declared reference does not resolve, leaving traceability incomplete" - but that explanation lived only in Explorer. Run
rac review --jsonin CI and you got the finding without the why.Now the impact sentence belongs to RAC itself. Every finding from
rac reviewcarries animpactfield - in the JSON, available to your scripts and pipelines, and rendered in Explorer from the very same source. One sentence, identical everywhere, maintained in one place.Why you care: if you pipe
rac review --jsoninto a dashboard, a bot, or a PR comment, you can now show your team why each finding deserves attention - not just that it exists. And the addition is purely additive: every existing field is untouched, so nothing you've built on the contract changes.Your editor, from the first minute
ehas always handed an artifact to your own editor. New in this release: the first time you launch Explorer, onboarding asks. One line, prefilled from your environment - press Enter to keep what$VISUAL/$EDITORalready says, type a command (code,vim, whatever you use) to set a preference, or Esc to skip entirely. Asked once, never again;/settingscan change it any time.Also in this release (since v0.8.9)
This tag carries v0.8.10, and it's a substantial one:
roadmaps/opens to reveal the folders inside it, nested exactly as on disk, with artifact counts on every directory. Your place survives reloads at any depth, and opening an artifact reveals it along its real path. Prefer the old views? Grouping cycles folders, type, and flat in/settings./new decision path/to/adr.mdpreviews the canonical template,yconfirms, and the ID is minted by the same machinery asrac new- nothing ever overwrites, and the new artifact opens ready fore./statsopens a dashboard - per-type validity, requirement and quality totals, decision status breakdowns, relationship counts - the same factsrac statsreports./browse decisionnow lists every decision in the filterable results panel, whatever grouping the sidebar is in.Upgrading
With pip:
pip install --upgrade 'requirements-as-code[explorer]' rac explorerWith uv:
(First time with uv, or if the upgrade can't see the new version yet:
uv tool install --reinstall --refresh 'requirements-as-code[explorer]'.)Everything is backward-compatible: existing files, commands, scripts, and preference files keep working exactly as before. The
rac review --jsonchange is additive - newimpactkey, sameschema_version, no existing field touched.This discussion was created from the release RAC v0.8.11 - the "why it matters" release.
Beta Was this translation helpful? Give feedback.
All reactions