Releases: caiopizzol/prq
Releases · caiopizzol/prq
v0.26.3
v0.26.2
Fixes
- Label filter crash — applying two mutually exclusive label filters no longer causes the render loop to iterate over an empty list, preventing a blank or corrupted interactive view.
v0.26.1
Fixes
- Interactive list cursor — clamps
selectedIndexto the visible (filtered) list before rendering, preventing an out-of-bounds crash that could occur after a nudge or in-progress toggle when filters were active.
v0.26.0
What's New
- Auto-relax config filters — when your configured filters would return an empty list,
prqnow drops the rightmost clauses one at a time until something matches, so you always see results instead of a blank queue. rto reset in filter menu — when the interactive filter menu is open, pressingrre-relaxes the config filter against whatever is currently loaded and jumps back to a useful view.- Filter relaxation feedback — both the interactive UI and plain output mode now tell you which clauses were dropped (e.g.
default filter relaxed: dropped label:future), so the adjustment is visible, not silent.
Improvements
- Selecting a filter value closes the menu — after picking a filter value or clearing a key, the menu closes so the next filter action starts fresh instead of stacking state.
handleFilterKeyextracted as a pure helper — filter key handling is now a standalone exported function, making it testable in isolation; 230+ lines of new tests cover bothfilter.tsandinteractive.ts.formatClausespreserves exclude prefix — the!prefix on exclude filters is correctly retained when filter clauses are formatted for display.
v0.25.0
What's New
- Linear integration — set
LINEAR_API_KEYandprqpulls your assigned Linear issues into the same queue alongside GitHub PRs and issues. No extra commands, no separate queue. sourcefilter key — slice the queue by origin withsource:linear,source:github, or their negations. Works with all existing filter syntax.
Improvements
- Linear issues display with Linear's team-prefixed identifier format (e.g.,
ENG-123) and a distinct Linear-purple badge — visually separate from GitHub items at a glance. - Issues with a
startedstate type land in In Progress; everything else lands in Requested — the same buckets, the same mental model. - Linear fetch failures are non-fatal — if the API call fails,
prqlogs the error to stderr and continues with GitHub results.
v0.24.1
Fixes
- Filter menu navigation — arrow keys and other navigation inputs now work while the filter menu is open; unhandled keys fall through to the main navigation handler instead of being swallowed.
v0.24.0
What's New
- Filter system —
--filterflag acceptskey:valuesyntax to narrow your queue bylabel,author,type,category,repo, ordraft; stack multiple flags for AND logic, comma-separate values for OR, prefix with!to exclude - Persistent filter defaults — add a
filtersarray to your config and--filterflags override it at runtime - Interactive filter menu — press
fin the TUI to open a two-step dimension/value picker; active filters highlight in the footer and toggle off with the same key - GitHub labels — labels from the search API now parse and display inline next to each item in both TUI and non-interactive output
- Changelog page —
prq.sh/changeloggenerates at build time from GitHub releases
Improvements
fetchQueueextracted — queue-fetching logic is now a standalone export from thestatuscommand, available for reuse by other commandsprq.shSEO — site ships withog:image,llms.txt,llms-full.txt,sitemap.xml, and JSON-LD structured data for better discoverability- AI-readable page content — screen-reader-only agent context added to web pages so AI tools get accurate information about
prqwhen crawling the site
v0.23.1
Fixes
- PR categorization — PRs you've reviewed that aren't stale and have no new commits now correctly appear as "waiting on others" with a
Reviewed, waiting on @authordetail, instead of being silently dropped from the queue. - Authored PRs with no reviewers — your open PRs with no requested reviewers now appear as "waiting on others" with a
No reviewers assigneddetail, instead of being silently dropped.
v0.23.0
Now I have everything I need.
What's New
defaultFilterconfig option — set"defaultFilter": "all" | "pr" | "issue"in your config to open the interactive view pre-filtered to a specific type.
Improvements
- Landing page layout — manifesto and install CTA now fit within a single viewport height using flexbox; no scroll required to reach the install command.
- Font loading — Google Fonts CSS is preloaded and
preconnecttofonts.gstatic.comis added; unused weights (300, 700) and the Inter family are removed. - Footer link hover — footer links animate with a purple dot and indent on hover; CSS-only, no JS.
- Version badge — badge now fetches the latest release tag from the GitHub releases API at runtime instead of hardcoding a version.
Fixes
- Contrast —
--dimand--midcolors bumped to pass WCAG 4.5:1 contrast ratio on both--bgand--surfacebackgrounds; copy button legibility improved. - Accessibility —
<main>landmark added; decorative intro text markedaria-hidden. - SEO — Open Graph and Twitter Card meta tags added; canonical URL,
robots.txt, andsitemap.xmlincluded. - Badge arrow animation — slide animation on the release badge arrow removed.
v0.22.0
What's New
- GitHub Issues support — assigned issues and mentioned issues appear alongside PRs in a unified attention queue, categorized by why they need you.
- Type filter — press
tto toggle between all items, PRs only, or issues only. PR/Issueprefix — each item shows its type inline, color-coded (purple for PRs, blue for issues) so the queue stays scannable at a glance.Mentionedcategory — new category surfaces issues and PRs where you've been tagged but have no other direct action.- Issue URL support —
github.com/org/repo/issues/123now resolves as a valid identifier alongside PR URLs.
Improvements
Needs Re-review→Needs Response— category name now covers both PR re-reviews and issue comment replies.Your PRs Waiting→Waiting on Others— broader name reflects that issues can also be waiting on a response from someone else.Requested Reviews→Requested— shorter label, same meaning.- Bot comment filtering — bot comments no longer count as activity that clears the needs-response state on issues.
- Reactions as acknowledgment — reacting to an issue comment counts as having acknowledged it, keeping the queue accurate.