docs: CHANGELOG 0.2.0 release + README roadmap refresh#249
Merged
DevanshuNEU merged 2 commits intoFeb 21, 2026
Conversation
CHANGELOG.md: - Added 0.2.0 release covering all work since 0.1.0 (Dec 2024) - 12 Added items: dependency graph overhaul, DSM matrix, team rules, docs overhaul, error boundary, test suite, SEO, GitHub import, settings, real-time indexing, search v3, feedback pipeline - 5 Changed items: dashboard redesign, NavLink fix, useQuery refactor, Docker env standardization, Repository type fix - 3 Removed items: ReactFlow stack, old graph components, jsdom - 5 Fixed items: object Object bug, search zoom, hover state, env comments, startup checks comment README.md: - Roadmap split into Shipped (12 items) and Coming Soon (5 items) - Added all recently shipped features that were missing Closes OPE-19, OPE-25
|
@DevanshuNEU is attempting to deploy a commit to the Dev's projects Team on Vercel. A member of the Team first needs to authorize it. |
📝 WalkthroughWalkthroughCHANGELOG.md updated from "Unreleased" to a dated 0.2.0 release (2026-02-20) with detailed Added/Changed/Removed/Fixed sections listing new features, breaking changes, and fixes. README.md reorganized the Roadmap into "Shipped" and "Coming Soon" subsections. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (2)
CHANGELOG.md (2)
11-22: Inconsistent PR references in the Added section.Lines 12 (Dependency Structure Matrix), 15 (React Error Boundary), and 16 (Frontend Test Suite) have no
(PR#xxx)citation, while all other Added items do. For traceability, consider adding the missing PR numbers.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@CHANGELOG.md` around lines 11 - 22, Add the missing PR references for the three entries: append the corresponding PR numbers to "Dependency Structure Matrix", "React Error Boundary", and "Frontend Test Suite" so their lines match the "(PR `#xxx`)" format used elsewhere; locate and update those exact headings ("Dependency Structure Matrix", "React Error Boundary", "Frontend Test Suite") in the changelog and insert the correct PR IDs (e.g., "(PR #...)" ) for traceability.
68-76: Consider adding version comparison link definitions per Keep a Changelog convention.The file declares it follows Keep a Changelog 1.1.0, which recommends reference-style link definitions at the bottom so
[0.2.0]and[0.1.0]headers link to the corresponding GitHub diff/tag.📝 Proposed addition (after line 76)
+ +[0.2.0]: https://github.com/OpenCodeIntel/opencodeintel/compare/v0.1.0...v0.2.0 +[0.1.0]: https://github.com/OpenCodeIntel/opencodeintel/releases/tag/v0.1.0🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@CHANGELOG.md` around lines 68 - 76, Add Keep a Changelog style reference link definitions at the bottom of CHANGELOG.md so release headers like [0.2.0] and [0.1.0] resolve to their GitHub compare/tag URLs; locate the "## Version History" section and append reference lines in the form "[0.2.0]: https://github.com/OWNER/REPO/compare/v0.1.0...v0.2.0" (and similar for other releases) for each published version, ensuring tags/compare ranges match the release headers used in the file.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@CHANGELOG.md`:
- Line 28: Update the CHANGELOG entry for the Docker env var rename to clearly
mark it as a breaking change: add a "**⚠️ Breaking**" label next to the line
describing "SUPABASE_KEY → SUPABASE_ANON_KEY" and append a short migration note
instructing self-hosted users to rename their environment variable from
SUPABASE_KEY to SUPABASE_ANON_KEY to avoid silent auth failures; keep the rest
of the line about added variables (SUPABASE_JWT_SECRET, VOYAGE_API_KEY,
COHERE_API_KEY, SENTRY_DSN) unchanged.
---
Nitpick comments:
In `@CHANGELOG.md`:
- Around line 11-22: Add the missing PR references for the three entries: append
the corresponding PR numbers to "Dependency Structure Matrix", "React Error
Boundary", and "Frontend Test Suite" so their lines match the "(PR `#xxx`)" format
used elsewhere; locate and update those exact headings ("Dependency Structure
Matrix", "React Error Boundary", "Frontend Test Suite") in the changelog and
insert the correct PR IDs (e.g., "(PR #...)" ) for traceability.
- Around line 68-76: Add Keep a Changelog style reference link definitions at
the bottom of CHANGELOG.md so release headers like [0.2.0] and [0.1.0] resolve
to their GitHub compare/tag URLs; locate the "## Version History" section and
append reference lines in the form "[0.2.0]:
https://github.com/OWNER/REPO/compare/v0.1.0...v0.2.0" (and similar for other
releases) for each published version, ensuring tags/compare ranges match the
release headers used in the file.
There was a problem hiding this comment.
🧹 Nitpick comments (1)
CHANGELOG.md (1)
1-8: Consider adding an[Unreleased]section and version comparison links per Keep a Changelog spec.The file declares compliance with Keep a Changelog 1.1.0 (line 5–6), but two standard conventions are absent:
[Unreleased]section — KaC recommends always keeping a placeholder at the top so new entries have a home before the next release.- Version comparison link references at the bottom — e.g.:
These turn the[0.2.0]: https://github.com/OpenCodeIntel/opencodeintel/compare/v0.1.0...v0.2.0 [0.1.0]: https://github.com/OpenCodeIntel/opencodeintel/releases/tag/v0.1.0[0.2.0]heading tokens into clickable diff links on GitHub.Neither is a blocker, but omitting both makes the claimed format compliance slightly misleading.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@CHANGELOG.md` around lines 1 - 8, Add a top-level "[Unreleased]" section and append version comparison link references for each released heading (e.g., the existing "[0.2.0] - 2026-02-20" token) so the CHANGELOG conforms to Keep a Changelog: insert an "## [Unreleased]" placeholder above the latest release heading for new entries, and add reference-style links at the bottom mapping each release token (e.g., "[Unreleased]", "[0.2.0]") to their GitHub compare/release URLs (e.g., compare v0.2.0 to previous tag and the release tag URL) so the headings become clickable diffs on GitHub.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Duplicate comments:
In `@CHANGELOG.md`:
- Line 28: Move the breaking-change callout to the start of the line and reword
the sentence for scannability: prepend a bold "Breaking:" marker (e.g.,
"**Breaking**:") at the beginning of the changelog entry, then state the change
— "Docker env vars standardized: SUPABASE_ANON_KEY replaces SUPABASE_KEY —
self-hosted users must rename SUPABASE_KEY to SUPABASE_ANON_KEY in their .env" —
and finally list the added vars (SUPABASE_JWT_SECRET, VOYAGE_API_KEY,
COHERE_API_KEY, SENTRY_DSN); update the line containing the current text "Docker
env vars standardized: SUPABASE_ANON_KEY replaces SUPABASE_KEY (**Breaking** --
self-hosted users must rename SUPABASE_KEY to SUPABASE_ANON_KEY in their .env).
Added SUPABASE_JWT_SECRET, VOYAGE_API_KEY, COHERE_API_KEY, SENTRY_DSN." so the
breaking notice is front-loaded and the message remains clear.
---
Nitpick comments:
In `@CHANGELOG.md`:
- Around line 1-8: Add a top-level "[Unreleased]" section and append version
comparison link references for each released heading (e.g., the existing
"[0.2.0] - 2026-02-20" token) so the CHANGELOG conforms to Keep a Changelog:
insert an "## [Unreleased]" placeholder above the latest release heading for new
entries, and add reference-style links at the bottom mapping each release token
(e.g., "[Unreleased]", "[0.2.0]") to their GitHub compare/release URLs (e.g.,
compare v0.2.0 to previous tag and the release tag URL) so the headings become
clickable diffs on GitHub.
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Update project documentation to reflect everything shipped since 0.1.0.
CHANGELOG.md
Added 0.2.0 release entry covering:
README.md
Roadmap updated:
Files changed: 2
Pure docs, zero code risk.
Linear
Closes OPE-19, OPE-25
Summary by CodeRabbit
New Features
Improvements
Bug Fixes
Chores