Skip to content

fix: exact tag matching, menu positioning, CI check, and cleanup#54

Merged
VariableThe merged 2 commits into
mainfrom
feat/release-0.5.2
Jun 24, 2026
Merged

fix: exact tag matching, menu positioning, CI check, and cleanup#54
VariableThe merged 2 commits into
mainfrom
feat/release-0.5.2

Conversation

@VariableThe

Copy link
Copy Markdown
Owner

Summary

  • Tag matching: Bulk delete/export by tag now uses exact tag matching instead of substring matching, preventing false positives
  • Menu positioning: Tag context menu now appears at the right-click location instead of a hardcoded position
  • RemindersPage: Removed dead sort code (completed tasks already filtered out)
  • CI: Version bump check now validates both package.json and tauri.conf.json independently
  • Cleanup: Removed unused @codemirror/autocomplete dependency (autosuggest uses ghost text instead)

Verification

  • npm run typecheck — clean
  • npm run lint — clean
  • npm run format:check — clean

- Fix tag bulk delete/export to use exact tag matching (not substring)
- Fix tag context menu position to use click coordinates
- Remove dead sort code in RemindersPage (completed tasks already filtered)
- Fix CI version bump check to handle package.json and tauri.conf.json independently
- Remove unused @codemirror/autocomplete dependency
@coderabbitai

coderabbitai Bot commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@VariableThe, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 17 minutes and 34 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more credits in the billing tab to continue.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 credits.

🚦 How do rate 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 see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: ae44a890-da36-4d56-b6e6-3ddaa6aa4034

📥 Commits

Reviewing files that changed from the base of the PR and between 89d278a and 12e5799.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (4)
  • .github/workflows/ci.yml
  • package.json
  • src/components/NoteSearch.tsx
  • src/components/RemindersPage.tsx
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/release-0.5.2

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@VariableThe VariableThe merged commit 10dfe45 into main Jun 24, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant