fixing upgrade dependencies step

[ParticularlyPythonicBS]

Summary by CodeRabbit

• Chores
  • Updated dependency management workflow to enhance consistency and reliability in how dependencies are resolved across development environments.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 06363302-6f33-4a6a-a92e-cba211218456

📥 Commits

Reviewing files that changed from the base of the PR and between 409def9 and f8d582d.

📒 Files selected for processing (1)

• .github/workflows/dependency-canary.yml

---

Walkthrough

The GitHub Actions dependency-canary workflow was updated to replace uv pip compile commands with uv export for generating requirements files. The generated requirements files are now sourced from the resolved lockfile rather than directly from pyproject.toml, while maintaining the same overall workflow sequence.

Changes

Cohort / File(s)	Summary
Dependency canary workflow .github/workflows/dependency-canary.yml	Replaced uv pip compile with uv export commands to generate requirements files from the lockfile instead of compiling pyproject.toml directly. Updated to run uv lock --upgrade, then export production and full-stack dependencies separately.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• ci: add dependency canary workflow #298: Initially introduced the dependency-canary workflow using uv pip compile; this PR updates it to use uv export for requirements generation.

Suggested labels

Maintenance

🚥 Pre-merge checks | ✅ 3

✅ 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 'fixing upgrade dependencies step' accurately describes the main change: updating the dependency upgrade workflow step from uv pip compile to uv export, which is a focused fix to the canary workflow.
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
• Commit unit tests in branch ci/fix_canary

---

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