chore: version bump v0.9.0#320
Conversation
WalkthroughBumps project version from 0.8.9 to 0.9.0 in dcs_core/version.py and pyproject.toml. No other files or logic changed. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Suggested labels
Suggested reviewers
Poem
Tip 🔌 Remote MCP (Model Context Protocol) integration is now available!Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats. ✨ Finishing Touches
🧪 Generate unit tests
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR/Issue comments)Type Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (1)
dcs_core/__version__.py (1)
15-15: Synced to 0.9.0 — consider eliminating dual maintenance of version strings.Keeping the version in both pyproject.toml and version.py invites drift. Optional improvements:
- Adopt a single source of truth via a build-time solution (e.g., poetry-dynamic-versioning) to generate version.py.
- Or read the installed distribution version at runtime to avoid manual bumps in two places.
Example (optional; keeps a fallback for editable installs):
+from importlib.metadata import PackageNotFoundError, version as _dist_version try: -__version__ = "0.9.0" + __version__ = _dist_version("dcs-core") +except PackageNotFoundError: + # Fallback for dev/editable environments; keep in sync with pyproject.toml + __version__ = "0.9.0"If you prefer a build-time approach, I can open a follow-up PR to wire up poetry-dynamic-versioning and remove the fallback. Want me to proceed?
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
💡 Knowledge Base configuration:
- MCP integration is disabled by default for public repositories
- Jira integration is disabled by default for public repositories
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (2)
dcs_core/__version__.py(1 hunks)pyproject.toml(1 hunks)
⏰ 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: Pytest Unit Tests with all supported python versions (3.12)
🔇 Additional comments (1)
pyproject.toml (1)
3-3: Version bump verified – no stale references detected &__version__alignedAll automated checks passed and no residual “0.8.9” references remain:
- Repository scan found zero occurrences of “0.8.9” in code, docs, Dockerfiles, Helm charts, or CI pipelines.
pyproject.tomlversion (0.9.0) matchesdcs_core/__version__.py(0.9.0).- The absence of a root‐package entry in
poetry.lockis expected—Poetry only locks dependencies, not the project itself.No downstream artifacts reference the old version. You’re good to merge.
Fixes/Implements
Description
Summary Goes here.
Type of change
Delete irrelevant options.
How Has This Been Tested?
Summary by CodeRabbit