Skip to content

v0.4.5 — fix: unique resource names (no more hardcoded ig-harness)

Choose a tag to compare

View all tags
@Shudesu Shudesu released this 25 Apr 14:01
· 31 commits to main since this release
v0.4.5
45352d7

Patch release. Critical fix for anyone with a prior deployment on the same Cloudflare account.

Fixed

  • Hardcoded resource names caused silent overwrite of existing Worker bindings. Previously scaffolder used `ig-harness` for the Worker, `ig-harness` for the D1 database, and `ig-harness-images` for the R2 bucket. On any account that already had an ig-harness Worker, re-running the scaffolder would silently re-bind the existing Worker to a new D1/R2, breaking the prior deployment.
  • Now generates a random 8-char hex suffix once per setup and applies it to all three resources: `ig-harness-` / `ig-harness--images`. Suffix is persisted in the state file so resumes pick the same names.

npm

  • `create-ig-harness@0.4.5` published

Upgrade

```bash
npx create-ig-harness@latest
```

Assets 2
Loading