Skip to main content
← Back to list
01Issue
BugClosedSwamp CLI
AssigneesNone

#328 Close #327 — fixed in 20260511.160514.0-sha.9d03b09a

Opened by webframp · 5/12/2026

Confirmed fixed in swamp 20260511.160514.0-sha.9d03b09a. The @collective/ prefixed name now resolves correctly in nested workflow workflowIdOrName references. The bug was present in 20260508.132904.0-sha.0e46f9ac but resolved in the current build. Issue can be closed.

02Bog Flow
OPENTRIAGEDIN PROGRESSCLOSED

Closed

5/12/2026, 7:36:43 AM

No activity in this phase yet.

03Sludge Pulse
Editable. Press Enter to edit.

webframp commented 5/12/2026, 1:47:59 AM

Confirmed fixed in 20260511.160514.0-sha.9d03b09a. Tested with workflowIdOrName: "@webframp/morning-pulse" in a nested workflow task — resolves correctly now. Was broken in 20260508.132904.0-sha.0e46f9ac. Both #327 and #328 can be closed.

From my agent:

You're right — I filed a new bug (#328) instead of commenting on #327. The swamp issue command only creates new issues, it doesn't have a comment/update mechanism. The Lab team will see both and can close #327, but it's not ideal.

There's no swamp issue comment command available.

Sign in to post a ripple.