fix(deno-runner): fail step when command exits non-zero #219

Merged

stack72 merged 1 commit from worktree-velvety-petting-floyd into main 2026-08-23 20:50:31 +00:00

Conversation 0 Commits 1 Files changed 4 +123 -6

stack72 commented 2026-08-23 13:57:14 +00:00

Owner

Copy link

Summary

• The run and task methods now throw when the underlying deno command exits with a non-zero exit code, causing the workflow step to correctly report failure
• The commandResult resource is still written before the throw so output is retrievable via swamp data get for debugging
• Version bumped to 2026.08.23.1 with upgrades entry, manifest and README updated to document the new behavior

Test plan

• 3 new tests verify run and task throw on non-zero exit while still persisting the output resource
• All 33 existing + new tests pass
• deno check, deno lint, deno fmt --check all clean
• deno install --frozen passes (lockfile unchanged)
• Local end-to-end via swamp extension source add to verify upgrade path from 2026.08.22.1

🤖 Generated with Claude Code

## Summary - The `run` and `task` methods now throw when the underlying deno command exits with a non-zero exit code, causing the workflow step to correctly report failure - The `commandResult` resource is still written before the throw so output is retrievable via `swamp data get` for debugging - Version bumped to `2026.08.23.1` with upgrades entry, manifest and README updated to document the new behavior ## Test plan - [x] 3 new tests verify `run` and `task` throw on non-zero exit while still persisting the output resource - [x] All 33 existing + new tests pass - [x] `deno check`, `deno lint`, `deno fmt --check` all clean - [x] `deno install --frozen` passes (lockfile unchanged) - [ ] Local end-to-end via `swamp extension source add` to verify upgrade path from `2026.08.22.1` 🤖 Generated with [Claude Code](https://claude.com/claude-code)

stack72 added 1 commit 2026-08-23 13:57:14 +00:00

fix(deno-runner): fail step when command exits non-zero ... f465af7810

The run and task methods captured the exit code in the commandResult
resource but never threw, so workflow steps always reported success
even when the underlying deno command failed.

Now both methods check the exit code after writing the resource and
throw if non-zero. The resource is still written first so output is
retrievable via swamp data get for debugging.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

stack72 merged commit fe346c0df3 into main 2026-08-23 20:50:31 +00:00

stack72 deleted branch worktree-velvety-petting-floyd 2026-08-23 20:50:31 +00:00

stack72 referenced this pull request from a commit 2026-08-23 20:50:32 +00:00

fix(deno-runner): fail step when command exits non-zero (#219)

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

swamp-club/swamp-extensions!219

No description provided.