fix: README.md [skip-release]#280
Conversation
📝 WalkthroughWalkthroughThe README's "Supported databases" table now specifies MSSQL Server supported versions as "2017, 2019, 2022, Azure SQL" instead of using a placeholder dash, clarifying database version compatibility for users. ChangesDocumentation Update
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (4 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 |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 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 `@README.md`:
- Line 79: The README claims "MSSQL Server" is a supported, stable DB with
restore support but the codebase contains no MSSQL implementation (no mssql
driver in package.json, only "mssql" as an enum value in the DB type list, no
connection handling, no migrations, no agent restore logic). Remove or downgrade
MSSQL from the supported table: either delete the MSSQL row or move it to a
"Planned" section and remove the ✅ and "restore" claim, and change "Azure SQL"
wording to "Azure SQL Database" if listed separately; update README.md and any
mention of the "mssql" enum in the DB type list to reflect planned/unimplemented
status so docs match code.
🪄 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: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: 46b005b9-3d0d-40c8-ab6a-0b9314c3f9a9
📒 Files selected for processing (1)
README.md
📜 Review details
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
- GitHub Check: build-and-test
- GitHub Check: Analyze (javascript-typescript)
Summary by CodeRabbit