v0.17.0 — per-site deploy keys for Bedrock clones

The clone wizard's Git-access step no longer shares one server key across every Bedrock repo — each site now brings its own read-only deploy key, generated on your machine and installed by SpinupWP as the new site's git identity.

Highlights

• A unique deploy key per site. GitHub attaches a deploy key to exactly one repository account-wide, so the old server-key approach stopped working at the second Bedrock repo cloned to a server ("key is already in use"). The Git-access step now generates a fresh keypair per repo, puts the public half on the repo (auto via gh, with the title spinup-<domain>@<server>), and sends the pair with the site create — clone as many Bedrock repos to one server as you like.
• Manual path included. No gh, or a repo off GitHub? The step shows each repo's generated key: o opens the repo's deploy-key settings page, and the new y copies the key to your clipboard.
• Private keys stay private. The pair lives in memory for the length of the wizard, is never written to config, and is registered with the clone log's redaction.

Notes

• Proven live end to end against a temporarily private repo where only the fresh per-site key could grant access — SpinupWP used it for the create-time clone and the full Bedrock clone passed.
• Keys already added by older versions keep working; they're simply no longer reused for new sites.

Update: git pull in your checkout (the global spinup symlink picks it up immediately).

Full changelog: v0.16.1...v0.17.0

🤖 Generated with Claude Code