bandicot

Deploy without a git repository

A project that only lives in Versions can now be checked and deployed from a saved version, with no commit and no repository anywhere.

Product

One key for Vercel, and your other keys follow

The Vercel entry now needs one saved key, the token. The first deploy finds or makes the project named after the folder. A second ready entry, Vercel environment, sends the saved keys you name, such as Stripe, the database and email, to the project's production settings, so nothing is pasted into a dashboard.

In the Versions window the Checks page shows the gate for the newest saved version, v12 for example, and Deploy sends exactly those files.

From a saved version to the host

Checks already ran on saved versions. Now the gate and the deploy do too. In a folder with no git history Bandicot deploys the newest saved version, or the one you name, by writing that version's files out and running your deploy command on them. The same rules hold as for a commit: the checks file is one you allowed, the result is signed, and every required check passed. A deployment set to go out on green goes out when the newest version passes.

Sending keeps up with you

When you record something new while a send is waiting on its checks, the send now checks the new head and goes out, instead of stopping and asking you to start again.