Repository navigation
fix: restore CI and prevent redirected image writes - #47
Conversation
|
🦞👀 Pull request received. I will update this pull request when review starts. ClawSweeper review completeClawSweeper finished reviewing this revision. The review result is being finalized. |
|
ClawSweeper status: review started. I am starting a fresh review of this pull request: fix: restore CI and prevent redirected image writes This is item 1/1 in the current shard. Shard 0/1. This temporary status tracks the active review worker. The completed review will appear in the durable ClawSweeper review comment. Crustacean status: shell secured, claws on keyboard, evidence pebbles being sorted. |
|
Merged as d9f70f4. Exact-head PR CI and post-merge main CI are green. Local proof under After updating Puppeteer: Independent Codex reviews found no actionable P0–P2 findings. Crabbox refused acquisition at fleet capacity (21/20), so the explicitly authorized lightweight local fallback was used. No release, tag, package-version bump, or deployment was performed. |
Repair the default-branch CI regression caused by an outdated synthetic model catalogue, harden Nano Banana image output against symlink redirection, and update Puppeteer Core from 25.12.0 to 25.13.0 with its matching browser protocol dependencies. The Node.js runtime requirement is unchanged.
The image writer now creates new outputs exclusively through pinned, no-follow directory handles. Existing files, hard links, dangling links, and symlinked parent components are rejected; explicit relative and absolute output directories remain supported. Multiple response images retain the previous last-image behavior. Thanks @DillyRabbit for reporting #46.
Validation:
Refs #46. No releases, tags, package-version bumps, or deployments.