Feat/16 migrate to uv

[AmanatAliPanhwer]

📌 Summary

Migrated this project to uv successfully with CI/CD pipelines, and everything.

---

🔧 Type of Change

• 🚀 New feature
• 🧾 Documentation update

---

🧩 Related Issues

Closes #16

---

🧠 Changes Introduced

• Migrated this project to uv
• Added the documentation for uv
• Changed Vercel deployment for uv
• Modified the Python GitHub action for uv.

---

✅ Checklist

• Tested locally without errors
• Documentation updated (if needed)
• Commits are descriptive and meaningful

Summary by CodeRabbit

• Documentation

  • Updated installation, setup, and usage instructions with new build tooling
  • Added testing section with test execution commands
  • Removed deployment-specific instructions
  • Added contributing guidelines

• Chores

  • Added Python version configuration file
  • Introduced comprehensive project configuration with metadata and dependencies
  • Consolidated dependency declarations

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
blog	Ready	Preview	Comment	Oct 17, 2025 2:54pm

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The changes migrate the project from traditional pip-based dependency management to the uv package manager. This includes adding Python version pinning, creating a standardized pyproject.toml with organized dependencies, and updating documentation to reflect the new workflow using uv sync and uv run commands.

Changes

Cohort / File(s)	Summary
Package Manager Configuration pyproject.toml, .python-version, requirements.txt	Introduces pyproject.toml with project metadata, runtime dependencies (Flask, Supabase, requests, etc.), and dev dependencies (pytest, playwright); pins Python version to 3.13; clears requirements.txt as dependencies migrate to pyproject.toml.
Documentation & Usage README.md	Replaces venv setup with uv installation; updates all commands to use uv sync (dependency installation), uv run app.py (running app), and uv run pytest (testing); removes PythonAnywhere deployment section; adds Tests and Contributing sections.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

The migration spans multiple configuration and documentation files that require cross-verification: ensuring all dependencies are correctly specified in pyproject.toml, dev dependencies are properly isolated, README instructions are accurate, and no runtime functionality is impacted by the tooling change.

Poem

🐰 A speedy uv speeds up our way,
Dependencies sorted—no more delay!
Dev tools and prod now neatly apart,
With pyproject guiding each Python start,
Version 3.13 pins the way forward—
This bundled approach? We all are rewarded! 🚀

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feat/16-migrate-to-uv

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 109d8a9 and 6a46e7a.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (4)

• .python-version (1 hunks)
• README.md (1 hunks)
• pyproject.toml (1 hunks)
• requirements.txt (0 hunks)

---

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