Skip to content

chore: use internal base URL for API client#67

Merged
Prashant-Surya merged 11 commits intocanaryfrom
chore/internal-url
Feb 13, 2026
Merged

chore: use internal base URL for API client#67
Prashant-Surya merged 11 commits intocanaryfrom
chore/internal-url

Conversation

@Prashant-Surya
Copy link
Member

@Prashant-Surya Prashant-Surya commented Feb 13, 2026

Description

Route PlaneClient API calls through PLANE_INTERNAL_BASE_URL when available, falling back to PLANE_BASE_URL.

Type of Change

  • Improvement (change that would cause existing functionality to not work as expected)

Test Scenarios

  • Verified in local by setting the env variables using mcp inspector

Summary by CodeRabbit

  • Chores
    • Version bumped to 0.2.3
    • Enhanced API base URL resolution to prioritize internal endpoint configuration when available, with automatic fallback to default settings

@coderabbitai
Copy link

coderabbitai bot commented Feb 13, 2026

📝 Walkthrough

Walkthrough

Updated base URL resolution in PlaneClient to prioritize PLANE_INTERNAL_BASE_URL environment variable, with fallback to PLANE_BASE_URL. Version bumped to 0.2.3.

Changes

Cohort / File(s) Summary
Base URL Resolution
plane_mcp/client.py
Updated base URL selection to prefer PLANE_INTERNAL_BASE_URL environment variable over PLANE_BASE_URL, with appropriate fallback logic.
Version Update
pyproject.toml
Bumped version from 0.2.2 to 0.2.3.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 Internal URLs now take the lead,
With fallbacks aplenty for every need,
Version steps forward, point-two-point-three,
Small tweaks of config, precise and free! ✨

🚥 Pre-merge checks | ✅ 4
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'chore: use internal base URL for API client' accurately describes the main change: updating the PlaneClient to prefer PLANE_INTERNAL_BASE_URL over PLANE_BASE_URL.
Docstring Coverage ✅ Passed Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Merge Conflict Detection ✅ Passed ✅ No merge conflicts detected when merging into canary

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch chore/internal-url

No actionable comments were generated in the recent review. 🎉


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 and usage tips.

@Prashant-Surya Prashant-Surya merged commit c9be035 into canary Feb 13, 2026
1 check 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.

3 participants