Prepare for release with version bump and dependency refresh

[RadCod3]

Purpose

Updates the pyproject files for the following package releases,

• afm-core: v0.3.0
• afm-cli: v0.4.0
• afm-langchain: v0.3.0

Also updates the 3rd party dependencies for latest fixes and security patches.
Note: uv audit was used to check vulnerable 3rd party dependencies.

Merge after #18

Summary by CodeRabbit

• Chores
  • Updated package versions for afm-cli (0.4.0), afm-core (0.3.0), and afm-langchain (0.3.0) with corresponding dependency constraints to ensure compatibility across the ecosystem.

[coderabbitai]

Walkthrough

Version bumps across three interdependent packages: afm-cli (0.3.0→0.4.0), afm-core (0.2.0→0.3.0), and afm-langchain (0.2.0→0.3.0). Dependency constraints updated to maintain compatibility.

Changes

Cohort / File(s)	Summary
Package Version Updates and Dependency Constraints python-interpreter/packages/afm-cli/pyproject.toml, python-interpreter/packages/afm-core/pyproject.toml, python-interpreter/packages/afm-langchain/pyproject.toml	Version bumps: afm-cli 0.3.0→0.4.0, afm-core 0.2.0→0.3.0, afm-langchain 0.2.0→0.3.0. Updated dependency constraints: afm-cli now requires afm-core==0.3.0 and afm-langchain>=0.3.0; afm-langchain now requires afm-core>=0.3.0,<0.4.0.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 Hop, hop, hooray! Versions climb so high!
From point-two to point-three, we reach for the sky!
Dependencies aligned, in harmony they dance,
A coordinated leap forward—no version mismatch! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description provides Purpose and context but lacks critical sections like Goals, Approach, and other required template sections, making it appear incomplete against the repository's template.	Expand the description to include Goals section explaining what problems these updates resolve, and Approach section detailing the testing methodology (e.g., uv audit results for third-party dependencies).

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Prepare for release with version bump and dependency refresh' accurately summarizes the main changes: version bumps for three packages and dependency updates.
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.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with 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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

🧹 Nitpick comments (1)

python-interpreter/packages/afm-cli/pyproject.toml (1)

14-15: Cap afm-langchain to the same release train as afm-core to prevent future resolver conflicts.

Line 14 pins afm-core==0.3.0, but Line 15 leaves afm-langchain>=0.3.0 unbounded. When afm-langchain 0.4.0 releases and requires afm-core>=0.4.0, this constraint will become unsatisfiable. Add an upper bound: afm-langchain>=0.3.0,<0.4.0.

Proposed diff

 dependencies = [
     "afm-core==0.3.0",
-    "afm-langchain>=0.3.0",
+    "afm-langchain>=0.3.0,<0.4.0",
 ]

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@python-interpreter/packages/afm-cli/pyproject.toml` around lines 14 - 15,
Update the afm-langchain dependency constraint in pyproject.toml so it is capped
to the same release train as afm-core: change the dependency declaration for
"afm-langchain>=0.3.0" to include an upper bound like
"afm-langchain>=0.3.0,<0.4.0" to avoid future resolver conflicts when
afm-langchain 0.4.x requires a newer afm-core; adjust the dependency string
where "afm-core==0.3.0" and "afm-langchain>=0.3.0" are declared.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@python-interpreter/packages/afm-cli/pyproject.toml`:
- Around line 14-15: Update the afm-langchain dependency constraint in
pyproject.toml so it is capped to the same release train as afm-core: change the
dependency declaration for "afm-langchain>=0.3.0" to include an upper bound like
"afm-langchain>=0.3.0,<0.4.0" to avoid future resolver conflicts when
afm-langchain 0.4.x requires a newer afm-core; adjust the dependency string
where "afm-core==0.3.0" and "afm-langchain>=0.3.0" are declared.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: dbaef8e7-b92f-4f86-9d2e-b26c56c6be3d

📥 Commits

Reviewing files that changed from the base of the PR and between cec1ace and 020d40a.

⛔ Files ignored due to path filters (1)

• python-interpreter/uv.lock is excluded by !**/*.lock

📒 Files selected for processing (3)

• python-interpreter/packages/afm-cli/pyproject.toml
• python-interpreter/packages/afm-core/pyproject.toml
• python-interpreter/packages/afm-langchain/pyproject.toml