Skip to content

deploy.py: a failed build stops before the upload - #6

Merged
thorwhalen merged 1 commit into
masterfrom
deploy-stops-on-failed-build
Oct 13, 2026
Merged

thorwhalen merged 1 commit into
masterfrom
deploy-stops-on-failed-build

Conversation

@thorwhalen

Copy link
Copy Markdown
Owner

Sprint review of #4 (deploy.py guarded behind __main__). The guard is right. One gap remained: the build and upload ran without check=True, so a failed build went on to upload whatever stale files were in dist/. Both now raise on failure, as i2mint/dacc's deploy.py already does. A test pins that a failed build uploads nothing.

deploy.py sits outside the package, so this merge should not release: the squash commit carries [skip ci].

Local: full suite green. Hosted checks: see below.

🤖 Generated with Claude Code

The build and upload ran without check=True, so a failed build went on to upload whatever
stale files were in dist/. Both now raise on failure (as dacc's deploy.py already does).
deploy.py is a manual script outside the package, so nothing is released.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@thorwhalen
thorwhalen merged commit a644ae5 into master Oct 13, 2026
12 checks passed
@thorwhalen
thorwhalen deleted the deploy-stops-on-failed-build branch October 13, 2026 06:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant