chore(release): v0.2.105

[teton-bot]

chore(release): v0.2.104 to v0.2.105

[coderabbitai]

Walkthrough

The workspace package version in Cargo.toml is bumped from 0.2.104 to 0.2.105, reflecting a routine release version increment with no functional changes to the codebase.

Changes

Cohort / File(s)	Summary
Workspace Version Bump Cargo.toml	Updated workspace package version from 0.2.104 to 0.2.105

Possibly related PRs

• smith#283: Sequential version bump in Cargo.toml workspace package (0.2.103→0.2.104 immediately preceding this 0.2.104→0.2.105 bump)
• smith#281: Identical code-level change updating workspace.package version in Cargo.toml
• smith#280: Same type of change updating the workspace.package version field in Cargo.toml

Suggested reviewers

• LudeeD
• Alw3ys
• dduuukk

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'chore(release): v0.2.105' directly and clearly summarizes the main change: updating the workspace package version to v0.2.105.
Description check	✅ Passed	The description 'chore(release): v0.2.104 to v0.2.105' is directly related to the changeset, clearly indicating the version bump from v0.2.104 to v0.2.105.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

---

---

📜 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 319577d and a89af84.

⛔ Files ignored due to path filters (1)

• Cargo.lock is excluded by !**/*.lock

📒 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: test

🔇 Additional comments (1)

Cargo.toml (1)

7-7: LGTM! Routine version bump.

The version increment from 0.2.104 to 0.2.105 is correctly formatted and consistent with the release PR objectives.

_{✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.}

---

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