update-backend-dependency

Prompt file imported from lmiguelvargasf/carda-coding-challenge (.github/prompts/update-backend-dependency.prompt.md). Copyright stays with the author.

Task:

• Confirm the dependency already exists in backend/pyproject.toml; if it does not, stop and ask before adding a new dependency.
• Resolve the latest stable version for the requested dependency from PyPI (source of truth) immediately before running any update command.
• Do not infer "latest" from backend/uv.lock, current pyproject.toml constraints, or local environment cache.
• From project root, run one command:
  • task backend:dep:add -- "<dependency>>=<latest_version>"
  • task backend:dep:add:dev -- "<dependency>>=<latest_version>"
• Do not manually edit dependency files; let uv add update them.
• uv add already syncs the environment; run task backend:install only if an extra sync is needed.

Constraints:

• Keep changes minimal and scoped.
• Update only the requested dependency unless explicitly asked to update more.
• Keep dependency name/extras unchanged; only move the minimum version floor.
• Prefer stable releases; use pre-releases only when explicitly requested.
• If PyPI cannot be reached or the latest stable version cannot be determined, stop and report the blocker instead of guessing.

Output:

• List changed tracked files.
• Expected files: backend/pyproject.toml and backend/uv.lock (explain extras).
• Include the resolved latest version, the PyPI source used, and the exact Taskfile command used.
• If no files changed, explicitly report that the dependency was already at the latest minimum version.