chore: post-merge housekeeping — TODO.md release status + graphify report refresh - #304
Conversation
…port refresh QNBS-v3: TODO.md documents PR #303's admin-bypass squash-merge to main; graphify-out/GRAPH_REPORT.md refreshed after the merge (7558 nodes, 14036 edges, 764 communities).
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
🏁 CodeAnt Quality Gate ResultsCommit: ✅ Overall Status: PASSEDQuality Gate Details
|
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 34 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. 📝 WalkthroughWalkthroughThe change updates pending release tracking for ChangesRelease tracking
Graph report regeneration
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Pull request overview
Post-merge housekeeping PR that updates the sprint TODO release status after PR #303 merged, and refreshes the checked-in Graphify report snapshot to reflect the current repo graph.
Changes:
- Updated
TODO.mdrelease section to record PR #303’s merge commit and clarify the remaining tag/publish hand-off step. - Refreshed
graphify-out/GRAPH_REPORT.mdwith updated corpus/graph statistics and navigation output.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| TODO.md | Updates the release tracker entry with PR #303 merge details and the remaining tag/publish step. |
| graphify-out/GRAPH_REPORT.md | Refreshes the Graphify-generated repository graph report snapshot. |
Suppressed comments (1)
graphify-out/GRAPH_REPORT.md:81
- Several other "God Nodes" entries are duplicated (
concat(),position(),set()each appear twice). This suggests the report is either not de-duplicating nodes by identity, or is collapsing distinct nodes into the same display name without disambiguation. Adjusting the generator to emit unique, disambiguated labels would make the ranking usable.
5. `concat()` - 66 edges
6. `concat()` - 66 edges
7. `position()` - 61 edges
8. `position()` - 61 edges
9. `set()` - 60 edges
10. `set()` - 60 edges
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
🧹 Nitpick comments (1)
graphify-out/GRAPH_REPORT.md (1)
71-81: 🗄️ Data Integrity & Integration | 🔵 Trivial | ⚡ Quick winDisambiguate repeated God Node labels.
The report lists
readInt32(),concat(),position(), andset()more than once with identical labels. If these are distinct nodes, include a source path or stable node ID. If they are the same node, prevent duplicate emission.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@graphify-out/GRAPH_REPORT.md` around lines 71 - 81, Update the God Nodes generation logic that produces the report entries so repeated labels are disambiguated with each node’s source path or stable ID, while ensuring the same underlying node is emitted only once. Preserve the existing ordering and edge counts for unique nodes.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@graphify-out/GRAPH_REPORT.md`:
- Line 167: Update the graph report generator that emits the “Nodes” list so
underscore-prefixed identifiers such as _emscripten_enter_soft_fullscreen() and
_glutInit() are wrapped in Markdown code spans or have their underscores
escaped. Preserve the existing node names and list formatting while ensuring the
generated Markdown passes MD037.
- Around line 328-330: Regenerate GRAPH_REPORT.md using the documented
graphifyy==0.8.26 version, replacing the committed report with that tool’s
output. Preserve the intentional distinction between filtered thin-community
counts and full Knowledge Gaps node sets, and do not manually edit the generated
content.
In `@TODO.md`:
- Around line 23-25: Update the release deployment note near the v1.25.0 tag
instruction to replace the guarantee that green build and e2e checks make deploy
succeed with wording that they allow deploy to run. Preserve the existing CI
prerequisite references and operational-safety qualification.
---
Nitpick comments:
In `@graphify-out/GRAPH_REPORT.md`:
- Around line 71-81: Update the God Nodes generation logic that produces the
report entries so repeated labels are disambiguated with each node’s source path
or stable ID, while ensuring the same underlying node is emitted only once.
Preserve the existing ordering and edge counts for unique nodes.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: a9b63a8e-99e2-4761-a3a2-a197386f9e98
📒 Files selected for processing (2)
TODO.mdgraphify-out/GRAPH_REPORT.md
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Root-causes 3 of 4 PR #304 review findings: the AST scanner was treating public/duckdb/duckdb-browser-eh.worker.js (a minified third-party bundle) as application source, polluting God Nodes (duplicate readInt32() entries), Communities (0.00-cohesion blobs of single-letter minified names), and Markdown output (unescaped _emscripten_enter_soft_fullscreen()/_glutInit() identifiers). - .graphifyignore: exclude public/duckdb/ - graphify-out/GRAPH_REPORT.md: regenerated with graphifyy==0.8.26 after excluding the vendor bundle; God Nodes/Communities now reflect only real application code - TODO.md: apply CodeRabbit wording fix ('so deploy can run' instead of 'so deploy succeeds', since green build+e2e only gate deploy, they don't guarantee actions/deploy-pages itself succeeds)
|
Fixed at 73eb30f: excluded |
|
@coderabbitai review |
✅ Action performedReview finished.
|
CI's doc-metrics drift gate correctly flagged the '⬜ Tag and publish v1.25.0' bullet as stale since v1.25.0 was already tagged and released. Flip to ✅ done with a GitHub Release link, and update the section header/status accordingly.
|
@coderabbitai review |
✅ Action performedReview finished.
|
Summary
TODO.md§ Release to record PR release: v1.25.0 — DuckDB excerpt encryption (SEC-6) + doc-truth fixes #303's admin-bypass squash-merge tomain(256264d3) and clarify the remaining tag/publish step.graphify-out/GRAPH_REPORT.mdafter the merge (7558 nodes, 14036 edges, 764 communities).No functional code changes — docs + generated report only.
🤖 Generated with Copilot
Summary by CodeRabbit
Documentation
Chores