deploy

Deploying Taskuary

A PyPI version can never be reused, even after deletion (RELEASING.md). Everything below is ordered so that nothing irreversible happens until the reversible things have all passed.

The one rule

Tag only after CI is green on the exact commit you are about to tag. The tag fires .github/workflows/publish.yml, and that upload is permanent. Pushing master is cheap and reversible; pushing a tag is not.

1. Know whose work you are shipping

A Taskuary coding agent commits to this same checkout, so git status is usually not just yours. Before anything else:

git status --short
git log --oneline origin/master..HEAD      # anything of mine not yet pushed

• If the owner said "push everything", the coder's in-flight work is included. Say so explicitly and list it — its own tests passing does not prove a half-built feature is finished.
• If they did not, commit only your own paths and leave theirs alone. Prove a shared file holds only your hunks: git diff --stat HEAD -- <file> (do the counts match what you wrote?) then git diff HEAD -- <file> | grep '^+' read against your own phrases.
• Commit through a temp index so a concurrent agent's staged work is never swept in:

export GIT_INDEX_FILE="$(pwd)/.git/claude-tmp-index"
rm -f "$GIT_INDEX_FILE"; git read-tree HEAD
git update-index --add -- <your paths>      # or `git add -A` for a deliberate ship-everything
TREE=$(git write-tree); PARENT=$(git rev-parse HEAD)
COMMIT=$(echo "$MSG" | git commit-tree "$TREE" -p "$PARENT")
git update-ref -m "release X" refs/heads/master "$COMMIT" "$PARENT"
rm -f "$GIT_INDEX_FILE"; unset GIT_INDEX_FILE
git reset -q                                # ALWAYS: refreshes the shared index to the new HEAD

Skipping that last git reset -q leaves the shared index showing your own files as modified and your new test file as deleted. It is confusing, not harmful — but fix it, do not commit over it.

2. Bump the version in all four places