How to ensure Leopard website remains up to date?

[towerofnix]

See #138 for a recent example of confusion because leopardjs.com is apparently running a version of Leopard/sb-edit from before 2021. I'm not familiar with the leopard-website codebase, and it doesn't appear to have any documentation—details on how to get it to "work" and for Leopard devs to keep the released site up to date would be appreciated!

Ideally I feel like it should be tied to NPM releases or something, right now it looks like it must take some manual intervention to update to the latest Leopard and sb-edit versions? Which apparently hasn't happened since before 2021 (see linked issue above), meaning any compatibility changes semi-recently introduced just aren't available to the general populace (including people testing recent Leopard additions).

/cc @PullJosh

[PullJosh]

The Leopard website installs sb-edit as a dependency. It always installs the latest version, but of course that only happens one time when the site is built (on Vercel). Then that version is locked in until the site is redeployed.

Maybe we could set up some kind of automation to redeploy the website when a new version of sb-edit is published. But I don't know how to do that.

The leopard version should always be up to date because the generated project code imports leopard from https://unpkg.com/leopard@^1/dist/index.esm.js. This URL always points to the most recent 1.x.x version of leopard. So even as we update leopard, previously generated projects will effectively get the new version retroactively (until a major version bump).

[PullJosh]

I just redeployed the website manually. (Required clicking one button.) Previous deployment was 336 days ago. Hopefully the latest sb-edit version is being used now?

[micahlt]

Receiving an error when redirecting to the Codesandbox.

{"error":"This endpoint requires the params `files` or `parameters` in order to work. See https://codesandbox.io/docs/importing#create-wizard for more details."}

Looks like no query params are being passed. Running latest Chrome on Windows 11.

[PullJosh]

@micahlt That is not a new issue. It also happened previously. Try with a different project.

[micahlt]

Gotcha - just assumed that it was related to the build. Sorry!