Skip to content

fix(panicbot): rename colon-named findings file + fail-loud filename guard - #350

Merged
hyperpolymath merged 2 commits into
mainfrom
fix/panicbot-colon-filename
Jul 1, 2026
Merged

fix(panicbot): rename colon-named findings file + fail-loud filename guard#350
hyperpolymath merged 2 commits into
mainfrom
fix/panicbot-colon-filename

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

Panicbot Sweep failed 3 consecutive weeks: actions/upload-artifact rejects : in paths and one legacy file (…/2026-02-14T00:00:00Z.json, the only colon path in the tree) sank the whole sweep's upload. Writer already emits colon-free names → renamed the residue + added a fail-loud pre-upload guard that names any future offender.

🤖 Generated with Claude Code

…guard

Panicbot Sweep failed 3 consecutive weekly runs (06-14/06-21/06-28):
actions/upload-artifact rejects ':' in paths, and one legacy file
(shared-context/findings/indieweb2-bastion/2026-02-14T00:00:00Z.json —
the only colon path in the tree) failed the whole sweep's artifact upload.

The writer (scripts/submit-finding.sh) already emits colon-free names
(%Y%m%d-%H%M%S), so the file is residue from an older path, not a live
writer bug — renamed to 2026-02-14T00-00-00Z.json. Added a fail-loud
pre-upload guard that names any future offender instead of letting the
upload step fail cryptically (fail loudly; the guard points at the writer).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@hyperpolymath
hyperpolymath enabled auto-merge (squash) July 1, 2026 21:40
@hyperpolymath
hyperpolymath disabled auto-merge July 1, 2026 22:07
@hyperpolymath
hyperpolymath merged commit d4a9aa1 into main Jul 1, 2026
13 checks passed
@hyperpolymath
hyperpolymath deleted the fix/panicbot-colon-filename branch July 1, 2026 22:07
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