chore: version bump to 0.9.9

[AnshumanX304]

Fixes/Implements

Description

Summary Goes here.

Type of change

Delete irrelevant options.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

• Locally Tested
• Needs Testing From Production

Summary by CodeRabbit

• Chores
  • Version 0.9.9 released with package configuration updates.

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

[coderabbitai]

Walkthrough

A simple version bump updating the package version from 0.9.8 to 0.9.9 across package metadata files without any functional or behavioral changes.

Changes

Cohort / File(s)	Summary
Version bump dcs_core/__version__.py, pyproject.toml	Updated module-level __version__ string and Poetry package version from 0.9.8 to 0.9.9

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• dcs-core#315: Performs the same version-bump change in identical files (dcs_core/__version__.py and pyproject.toml).
• dcs-core#307: Updates the same version strings in both dcs_core and pyproject configuration for package versioning.
• dcs-core#341: Directly modifies the same version declarations to bump the package version.

Suggested labels

Review effort 1/5

Suggested reviewers

• Ryuk-me
• rishav2803

Poem

🐰 A version hops from eight to nine,
Tiny changes, clean and fine,
Two small files in perfect rhyme,
One point-oh, marking time! ✨

Pre-merge checks and finishing touches

✅ 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 'chore: version bump to 0.9.9' clearly and accurately describes the primary change across all modified files (version updates in dcs_core/version.py and pyproject.toml).
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 98f63c0 and add70e7.

📒 Files selected for processing (2)

• dcs_core/__version__.py (1 hunks)
• pyproject.toml (1 hunks)

🔇 Additional comments (2)

dcs_core/__version__.py (1)

15-15: Version update is consistent across files.

The __version__ string has been correctly updated to "0.9.9", matching the version in pyproject.toml. This maintains consistency for tools and modules that reference the version at runtime.

pyproject.toml (1)

3-3: The repository cloning failed due to a network/server error, preventing me from executing the verification script. I cannot access the codebase to:

1. Search for other version references (0.9.[0-8]) that may need updating
2. Verify if dcs_core/__version__.py or other version files were updated consistently
3. Check if a changelog or release notes were updated

Unable to verify version consistency across the codebase due to infrastructure constraints.

Without access to the repository, I cannot confirm whether:

• All version references have been updated from 0.9.8 to 0.9.9
• The patch-level bump is semantically appropriate
• Related files (changelog, version constants) are in sync

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Add release notes and update PR description.

The version bump lacks accompanying documentation. A proper release should include a changelog entry describing what's included in v0.9.9 (bug fixes, new features, breaking changes, etc.).

The PR description is also placeholder boilerplate. Update it to document the scope of this release for users and maintainers. Additionally, if the repository maintains a CHANGELOG file, add an entry for v0.9.9 with user-facing release notes.

🤖 Prompt for AI Agents

In pyproject.toml around line 3, the version was bumped to "0.9.9" but no
release notes or PR description were provided; update the repository by adding a
user-facing changelog entry for v0.9.9 describing bug fixes, new features, and
any breaking changes, update the PR description to summarize the scope and
impact of the release, and if a CHANGELOG.md (or similar) exists add a properly
formatted v0.9.9 entry with dates and concise notes so maintainers and users can
understand what changed.