For the complete documentation index, see llms.txt. This page is also available as Markdown.

Release readiness check

Find release problems while there is still time to fix them. A scheduled release check verifies migrations, feature flags, the changelog, and the docs before each release window.

Goal: Find release problems early, while there is still time to fix them.

What it does

Before each release window, a schedule verifies the checklist: migrations are clean, feature flags are set correctly, the changelog is drafted, and the docs are up to date. Running it ahead of the release means problems surface early, while there is still time to fix them.

The plugin

tessl/release-check walks your release checklist against the changes since the last release and reports what is missing. Install it with:

$ tessl install tessl/release-check

Define the schedule

Run it every Thursday at 10:00 UTC, ahead of a Friday release. Add this entry to the schedules block in your project's tessl.json, and keep any other entries already in that block. Replace production with the name of your environment (see the Schedules overview for the prerequisites).

1

Add the schedule entry

{
  "schedules": {
    "release-check": {
      "skill": "tessl/release-check",
      "schedule": "weekly on thursday at 10:00",
      "environment": "production"
    }
  }
}
2

Validate and push

Validation always checks the local file. For an authenticated linked project that can reach Tessl, it also gives an advisory warning when current workspace capacity may not accommodate additional schedules. Commit and push the change, then confirm Tessl applied the schedule in your workspace before checking its run history.

$ tessl schedule validate
$ git add tessl.json
$ git commit -m "chore(docs): add release check schedule"
$ git push
3

Check the runs

Open the schedule in the web app, or run tessl schedule runs <id> to see its run history.

Customize with instructions

Match your own checklist by adding instructions to the same schedule entry. Keep all other entries in the schedules block:

{
  "schedules": {
    "release-check": {
      "skill": "tessl/release-check",
      "schedule": "weekly on thursday at 10:00",
      "environment": "production",
      "instructions": "Check that all migrations have a rollback and every new flag has a default"
    }
  }
}

Create your own

Want a different checklist? Create your own plugin that walks your release checklist and reports what is missing.

Last updated