Rebuild and publish playground after releases

[mdjermanovic]

Ideally, after each ESLint release the playground would be automatically re-built with the new version of ESLint and published.

This looks like a good case for the use of Netlify build hooks, assuming that the build hooks trigger all of build -> deploy -> publish.

[nzakas]

Build hooks only rebuild what’s in the repo already. We would also need a way to update the ESLint version in package.json. I was going to check and see if there was a way to trigger a GitHub workflow based on a release in another repo. Worst case, we could build this into the bot.

[mdjermanovic]

Version in the root is used to lint the playground repo.

The version we're building the playground from is in src/playground/node_modules/eslint. It's always installed by the build script as "eslint": "latest". A full rebuild should do the work without the need to update anything in the repo. A problem could be only Netlify's change detection if it applies when the build is triggered by a hook.

[mdjermanovic]

I've just tried with a build hook and it has successfully published playground with ESLint v8.18.0

[nzakas]

Oh nice! 🎉 So I guess all we need is a workflow to trigger the build hook on release?

[mdjermanovic]

all we need is a workflow to trigger the build hook on release?

Yes, that should work well in this case

[mdjermanovic]

eslint/eslint#16034