For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt, and this page is available as Markdown at /automations/overview/example-schedules/use-case-release-check.md.
Docs

    Release readiness check

    Info

    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).

    Add the schedule entry

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

    Validate and push

    Signed out, validation checks the local file only. Signed in, with a name that identifies your project, it also runs the checks Tessl applies when the file syncs and when a run starts. 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

    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 inside the same entry's action. Keep all other entries in the schedules block:

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

    Create your own

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