@elalfner/relevo 0.9.2 → 0.9.3

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "relevo",
   "displayName": "Relevo",
-  "version": "0.9.2",
+  "version": "0.9.3",
   "description": "An automatic issue-to-merge workflow where an agent builds and people verify.",
   "author": {
     "name": "Elias Alfaro"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@elalfner/relevo",
-  "version": "0.9.2",
+  "version": "0.9.3",
   "description": "Relevo: an automatic issue-to-merge workflow where an agent builds and people verify.",
   "type": "module",
   "license": "MIT",

package/scripts/lib/doctor.mjs

@@ -767,7 +767,7 @@ function shipChecks(f) {
 
 // The action that sets up the toolchain of a stack in the build job of the go workflow. Vue needs only Node, which the
 // job installs for Relevo itself, and a stack that is not listed here is not judged.
-const TOOLCHAIN_ACTIONS = { flutter: { action: 'subosito/flutter-action', step: 'the Flutter step' }, laravel: { action: 'shivammathur/setup-php', step: 'the Laravel step' } };
+const TOOLCHAIN_ACTIONS = { flutter: { action: 'subosito/flutter-action', step: 'the Flutter step' }, laravel: { action: 'shivammathur/setup-php', step: 'the Laravel step' }, supabase: { action: 'supabase/setup-cli', step: 'the Supabase step' } };
 
 /**
  * Does the go workflow install the toolchain of each configured platform? Without it every cloud build fails QA after

package/scripts/lib/init.mjs

@@ -334,7 +334,7 @@ export function planInit({ facts, answers, templates, current, admin, upgrades =
       items.push(item(`workflow.${file}`, 'differs', `.github/workflows/${file} differs from the template and could not be checked for an update (${up.message}); it is left as it is`));
     } else {
       // The cloud build only passes QA when the build job installs the toolchain of the stack, which the template does.
-      const toolchain = file === 'relevo-go.yml' ? '; check that its build job installs the toolchain of your stacks, as the template does for Flutter and Laravel' : '';
+      const toolchain = file === 'relevo-go.yml' ? '; check that its build job installs the toolchain of your stacks, as the template does for Flutter, Laravel and Supabase' : '';
       items.push(item(`workflow.${file}`, 'differs', `.github/workflows/${file} exists and differs from the template; it is left as it is (compare it by hand${toolchain})`));
     }
   });

package/skills/init/SKILL.md

@@ -34,7 +34,7 @@ If `relevo.yml` already exists and is valid, skip this step. Otherwise ask, in s
 - who builds and reviews (GitHub usernames) and who writes the specs;
 - the review mode: `none` (a solo project), `peer` or `roles`;
 - the language of the hand-off messages (`en` or `es`);
-- the platforms: for each one a name, its stack (look at the project to propose one: the profiles in `${CLAUDE_PLUGIN_ROOT}/stacks/` are the stacks Relevo ships with: `flutter`, `vue`, `laravel` and `supabase`), the folder where it lives (`.` for a repository with one platform, `apps/web` in a monorepo) and, for a stack that has targets, which ones (for Flutter: `android`, `ios`, `web`; for Vue: `web`; Laravel and Supabase have none). Several platforms in one repository are written down, but `go` builds only a repository with one for now;
+- the platforms: for each one a name, its stack (look at the project to propose one: the profiles in `${CLAUDE_PLUGIN_ROOT}/stacks/` are the stacks Relevo ships with: `flutter`, `vue`, `laravel` and `supabase`), the folder where it lives (`.` for a repository with one platform, `apps/web` in a monorepo) and, for a stack that has targets, which ones (for Flutter: `android`, `ios`, `web`; for Vue: `web`; Laravel and Supabase have none). Several platforms in one repository are supported: each issue names the platform it is for with a `Platform:` line, and `go` builds that one;
 - where `go` builds: in the cloud, on each person's machine, or both (the default), and, for the cloud, with an API key from the Anthropic Console (the default) or with a subscription token. A subscription's quota is shared by every run and by the interactive use of the account, so `init` sets `limits.concurrent_agents` to 1 for it. Nothing about this goes in `relevo.yml` apart from that number: the installed workflows, the secret that exists and the repository variable `RELEVO_CLOUD_GO` (`off` pauses the cloud at once, with no pull request) decide it. Whatever the answer, the ship workflow (`relevo-ship.yml`) is added: it ships an approved issue when a person applies the `relevo:ship` label, runs no model and needs no model credential, and the repository variable `RELEVO_CLOUD_SHIP` (`off`) pauses it;
 - whether the repository runs its GitHub Actions on a self-hosted runner. Ask nothing more when the answer is no: the workflows run on `ubuntu-latest` and `relevo.yml` gets no `runner` key. On a yes, ask for the runner's labels (for example `self-hosted` and `linux-build`): they become `runner.labels` in `relevo.yml` and the `runs-on` of every workflow `init` adds. Say that Relevo assumes a self-hosted runner keeps its files between jobs, whatever the person says about it, and that the agent's code runs with the permissions of the runner's user; do not ask whether the runner is ephemeral;
 - the repositories this one depends on, if any (`owner/repo`, for example the back end of a front end): they are written to `links`, the closed list that `Depends-on: owner/repo#N` is checked against;

package/templates/workflows/relevo-digest.yml

@@ -1,4 +1,4 @@
-# relevo-template: 0.9.2
+# relevo-template: 0.9.3
 # Relevo: posts one digest per working day, as a comment on the issue named by digest.issue in relevo.yml.
 # It lists who is waiting on what and the alerts, and posts nothing when nothing is waiting.
 # Subscribe your chat tool to that issue to receive it. Copy to .github/workflows/relevo-digest.yml.
@@ -14,7 +14,7 @@ name: relevo-digest
 # The version of @elalfner/relevo whose scripts this workflow runs. The plugin's templates carry the version they
 # were released with, and `/relevo:init` reports this file as different when it is older; change it by hand to update.
 env:
-  RELEVO_VERSION: '0.9.2'
+  RELEVO_VERSION: '0.9.3'
 
 on:
   schedule:

package/templates/workflows/relevo-go.yml

@@ -1,4 +1,4 @@
-# relevo-template: 0.9.2
+# relevo-template: 0.9.3
 # Relevo: builds an issue when someone with write access labels it `relevo:ready`.
 # Copy to .github/workflows/relevo-go.yml. If you renamed the ready label in relevo.yml, change it below too.
 #
@@ -20,7 +20,7 @@ name: relevo-go
 # The version of @elalfner/relevo whose scripts this workflow runs. The plugin's templates carry the version they
 # were released with, and `/relevo:init` reports this file as different when it is older; change it by hand to update.
 env:
-  RELEVO_VERSION: '0.9.2'
+  RELEVO_VERSION: '0.9.3'
   # The version of OpenSpec that the job installs for itself.
   OPENSPEC_VERSION: '1.14.3'
 
@@ -143,8 +143,8 @@ jobs:
       # issue is installed here. The `decide` job tells which one (`needs.decide.outputs.stack`) and where it lives
       # (`needs.decide.outputs.path`), so an issue for the front does not install the back's tools: a step whose stack
       # is not the issue's is skipped and costs nothing. The names are the `stack` of relevo.yml. Change the versions
-      # and the caching to suit the project; `/relevo:doctor` fails when a Flutter or Laravel platform has no active
-      # step below, because every build would fail QA after spending the run.
+      # and the caching to suit the project; `/relevo:doctor` fails when a Flutter, Laravel or Supabase platform has no
+      # active step below, because every build would fail QA after spending the run.
       - if: needs.decide.outputs.stack == 'flutter'
         uses: subosito/flutter-action@v2
         with:
@@ -155,6 +155,11 @@ jobs:
         with:
           php-version: '8.3'
           tools: composer
+      # Supabase: the CLI runs the checks of the profile against containers on the runner, which already has Docker.
+      - if: needs.decide.outputs.stack == 'supabase'
+        uses: supabase/setup-cli@v1
+        with:
+          version: latest
       # Vue needs only Node, which this job installed above; to cache the packages, uncomment:
       #   - if: needs.decide.outputs.stack == 'vue'
       #     uses: actions/setup-node@v4

package/templates/workflows/relevo-queue.yml

@@ -1,4 +1,4 @@
-# relevo-template: 0.9.2
+# relevo-template: 0.9.3
 # Relevo: re-evaluates the queue and starts the issues that are now eligible.
 # Copy to .github/workflows/relevo-queue.yml next to relevo-go.yml (it starts builds through that workflow).
 #
@@ -15,7 +15,7 @@ name: relevo-queue
 # The version of @elalfner/relevo whose scripts this workflow runs. The plugin's templates carry the version they
 # were released with, and `/relevo:init` reports this file as different when it is older; change it by hand to update.
 env:
-  RELEVO_VERSION: '0.9.2'
+  RELEVO_VERSION: '0.9.3'
 
 on:
   issues:

package/templates/workflows/relevo-review.yml

@@ -1,4 +1,4 @@
-# relevo-template: 0.9.2
+# relevo-template: 0.9.3
 # Relevo: keeps the issue label in step with its pull request.
 # A review that requests changes sets `relevo:changes-requested` and mentions the author; a new push returns the
 # issue to `relevo:pr-open`; an approval mentions the person who will run /relevo:ship.
@@ -15,7 +15,7 @@ name: relevo-review
 # The version of @elalfner/relevo whose scripts this workflow runs. The plugin's templates carry the version they
 # were released with, and `/relevo:init` reports this file as different when it is older; change it by hand to update.
 env:
-  RELEVO_VERSION: '0.9.2'
+  RELEVO_VERSION: '0.9.3'
 
 on:
   pull_request_review:

package/templates/workflows/relevo-ship.yml

@@ -1,4 +1,4 @@
-# relevo-template: 0.9.2
+# relevo-template: 0.9.3
 # Relevo: ships an issue when a person applies the `relevo:ship` label to it.
 # Copy to .github/workflows/relevo-ship.yml. If you renamed the ship label in relevo.yml, change it below too.
 #
@@ -27,7 +27,7 @@ name: relevo-ship
 # The version of @elalfner/relevo whose scripts this workflow runs. The plugin's templates carry the version they
 # were released with, and `/relevo:init` reports this file as different when it is older; change it by hand to update.
 env:
-  RELEVO_VERSION: '0.9.2'
+  RELEVO_VERSION: '0.9.3'
   # The version of OpenSpec that the job installs for itself.
   OPENSPEC_VERSION: '1.14.3'
 

package/templates/workflows/relevo-sla.yml

@@ -1,4 +1,4 @@
-# relevo-template: 0.9.2
+# relevo-template: 0.9.3
 # Relevo: reminds the reviewer when a pull request waits longer than limits.review_sla_hours, and escalates
 # to the spec writer (adding the needs-reviewer label) after the same time again.
 # Copy to .github/workflows/relevo-sla.yml. Needs a relevo.yml at the repository root.
@@ -13,7 +13,7 @@ name: relevo-sla
 # The version of @elalfner/relevo whose scripts this workflow runs. The plugin's templates carry the version they
 # were released with, and `/relevo:init` reports this file as different when it is older; change it by hand to update.
 env:
-  RELEVO_VERSION: '0.9.2'
+  RELEVO_VERSION: '0.9.3'
 
 on:
   schedule: