Repository navigation
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 37bb19cd3e
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| trending: recent >= TRENDING_MIN_RECENT_INSTALLS, | ||
| score: recent / (ageDays + 2) ** TRENDING_GRAVITY, |
There was a problem hiding this comment.
Expire stale recent-install signals before ranking
When the stats sidecar stops refreshing, the server deliberately retains the stored statsJson after fetch failures, but this ranking treats its recentInstalls as current forever and never considers the sidecar's generatedAt. A plugin that once crossed the five-install threshold therefore remains in the privileged trending cohort indefinitely—even weeks after the cached window ceased being recent—and can continue outranking newly published plugins. Preserve the generation timestamp and ignore or age out recentInstalls once the snapshot is stale.
Useful? React with 👍 / 👎.
Optional plugins (install on request or off by default) come first and plugins on by default come last, each newest first. The order is computed once by the bundled catalog generator, which replaces runtime trending and the recentInstalls stats field. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Human comments
What was wrong
The BB Official shelf listed plugins in bundled-registry order, so its first cards never changed. Most of those cards were plugins every user already has. Production web builds also omitted publication dates because their checkout was shallow.
What changed
bb plugin searchand getbb.app all read the same order.How you verified
52dc5f8d9: 45 passed and 3 skipped. A flaky Windows host-daemon timing test passed on rerun. Run52dc5f8d9.BB Official shelf · bb app and getbb.app
Before: 59a1fcc (equivalent to base e9ad6b0 for these surfaces; the only change between them is under
apps/web/src/guides) · After: 52dc5f8 · Captured at 2×BB-Thread-ID: thr_kxipfsmu7x
🤖 Generated with Claude Code