chore: bump version to 2.1.0 for new release

[rishitank]

Summary

Bumps version from 2.0.1 to 2.1.0 to trigger a new release.

Why was the release skipped?

The Release workflow ran after PR #1 was merged, but all jobs (except check) were skipped because:

1. The workflow detected that tag v2.0.1 already exists
2. Since the version in Cargo.toml (2.0.1) matches an existing tag, no release was needed
3. This is the correct behavior - the workflow only releases when there's a new version

What this PR does

Bumps the version to 2.1.0 to trigger a proper release that includes all the new features from PR #1:

• Complete MCP specification (2025-11-25) implementation
• 70+ tools across Navigation, Workspace, Search, Memory, and Skills categories
• Agent Skills framework with 7 built-in skills
• Multi-language symbol detection (Rust, Python, TypeScript/JavaScript, Go)
• Security fixes (path traversal protection, regex escaping, canonical paths)
• Workflow improvements (Release, Dependabot, SDK Sync)
• 244 unit tests + integration tests

After merge

Once this PR is merged:

1. CI will run on main
2. Release workflow will be triggered by workflow_run
3. check job will detect new version 2.1.0 without existing tag
4. Build, changelog, and release jobs will run
5. GitHub Release v2.1.0 will be created with binaries

---

Pull Request opened by Augment Code with guidance from the PR author

Summary by CodeRabbit

Release Notes

Version 2.1.0

• Chores
  • Version updated to 2.1.0

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

The package version in Cargo.toml has been incremented from 2.0.1 to 2.1.0. This is a minor version bump with no code or functional changes.

Changes

Cohort / File(s)	Summary
Version bump Cargo.toml	Package version updated from 2.0.1 to 2.1.0

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 Hop! The version climbs up high,
From point-oh-one to minor-sky,
A simple bump, a gentle nudge,
No code to fudge, no logic budge!
Two-point-one now takes the stage, 🎉

Pre-merge checks

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and directly summarises the main change: a version bump from 2.0.1 to 2.1.0 for release purposes, which aligns perfectly with the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 99cecbf and 0507a43.

📒 Files selected for processing (1)

• Cargo.toml

⏰ 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). (1)

• GitHub Check: build

🔇 Additional comments (1)

Cargo.toml (1)

3-3: LGTM! Version bump is correctly formatted.

The version update to 2.1.0 follows semantic versioning correctly, and the v2.1.0 tag does not yet exist in the repository.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}