diff --git a/.claude/skills/cutting-a-release/SKILL.md b/.claude/skills/cutting-a-release/SKILL.md index fa41973d3..e196f96b4 100644 --- a/.claude/skills/cutting-a-release/SKILL.md +++ b/.claude/skills/cutting-a-release/SKILL.md @@ -225,12 +225,27 @@ required" — that is the note that sends someone digging through `git log`: > for tool rows written before it existed. Idempotent; dry-run by default. > > ```bash -> AWS_PROFILE= python backend/scripts/backfill_tool_catalog_index.py \ +> AWS_PROFILE= backend/.venv/bin/python backend/scripts/backfill_tool_catalog_index.py \ > --table -app-roles --region us-west-2 --apply > ``` > -> Verify `skipped=0 failed=0` and that the index item count matches the tool -> count before considering the deploy complete. +> Verify `skipped=0 failed=0`, then confirm with a live Query on the index. + +Two details that cost real time on the v1.21.0 prod run, both worth carrying +into whatever backfill note you write: + +- **Give the backend venv's interpreter, not a bare `python`.** These scripts + need `boto3`, which is not in the system Python — a bare `python` fails with + `ModuleNotFoundError: No module named 'boto3'` before it does anything. All + six `backfill_*.py` scripts are runnable as + `backend/.venv/bin/python backend/scripts/