@sjawhar/claude-envoy 1.12.0 → 1.12.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -2,5 +2,5 @@
2
2
  "name": "claude-envoy",
3
3
  "description": "Deliver Envoy events as Claude Code channel notifications and expose Envoy MCP tools.",
4
4
  "mcpServers": "./.mcp.json",
5
- "version": "1.12.0"
5
+ "version": "1.12.1"
6
6
  }
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "claude-envoy",
3
- "version": "1.12.0",
3
+ "version": "1.12.1",
4
4
  "description": "Deliver Envoy events as Claude Code channel notifications and expose Envoy MCP tools.",
5
5
  "mcpServers": {}
6
6
  }
@@ -55145,7 +55145,7 @@ var import_nats2 = __toESM(require_mod4(), 1);
55145
55145
 
55146
55146
  // package.json
55147
55147
  var name = "@sjawhar/claude-envoy";
55148
- var version2 = "1.12.0";
55148
+ var version2 = "1.12.1";
55149
55149
  var legion = {
55150
55150
  daemonApiVersion: 55
55151
55151
  };
@@ -55,13 +55,17 @@ other change to the head voids it.
55
55
  (`gh api repos/<o>/<r>/commits/<headRefOid>/check-runs --paginate --jq '.check_runs[] | [.name, .status, .conclusion] | @tsv'`):
56
56
  every required name present, `completed` and `success` (GitHub counts `neutral` and `skipped`
57
57
  as passing for a required check). A required check
58
- `queued` or `in_progress`: wait. One `completed` as `cancelled`, or absent: re-run that run's
58
+ `queued` or `in_progress`: wait. One `completed` as `cancelled`, or absent: on a `pull_request`
59
+ run, re-run that run's
59
60
  failed and cancelled jobs, once, then wait — never the whole run, which runs again every job that
60
- succeeded too. Find the run and job at the head: the head's runs
61
+ succeeded too. A merge-group run is never re-run: the implementer finishes its round instead,
62
+ and the pull request is tested again when it is queued again.
63
+ Find the run and job at the head: the head's runs
61
64
  (`gh api 'repos/<o>/<r>/actions/runs?head_sha=<headRefOid>&per_page=100' --jq '.workflow_runs[] | [.id, .name, .event, .status, .conclusion] | @tsv'`),
62
65
  then each candidate run's jobs
63
66
  (`gh api repos/<o>/<r>/actions/runs/<run-id>/jobs --jq '.jobs[] | [.id, .name, .status, .conclusion] | @tsv'`).
64
- A cancelled job: `gh run rerun <run-id> --failed`, which GitHub applies to the run's failed and
67
+ A cancelled job of a pull-request run: `gh run rerun <run-id> --failed`, which GitHub applies to
68
+ the run's failed and
65
69
  cancelled jobs and the jobs that depend on them, and to nothing that succeeded. Never
66
70
  `--job <job-id>` alone: under a routing workflow, re-running only the final job reads the
67
71
  cancelled results again and stays red. GitHub refuses a re-run while an attempt of that run is
@@ -54,11 +54,11 @@ gives them).
54
54
  Under the Go daemon a check or workflow the base branch requires that settles red on the head,
55
55
  before the completion or after it, sends the work back to `implementing` with the failing checks
56
56
  named, until `max_fix_attempts` is spent, when the architect decides. The one CI result an implementer waits for is a re-run: when its task names a red that
57
- failed on its own, it re-runs the failed jobs once (`gh run rerun <run-id> --failed`) and completes once
57
+ failed on its own in a `pull_request` run, it re-runs the failed jobs once (`gh run rerun <run-id> --failed`) and completes once
58
58
  the re-run settles green, woken by the pull request's checks event (`skill://envoy`, *Wait for
59
- CI or a merge*: subscribe, then end the turn), never by a sleep loop. A completion while that red
60
- still stands is sent back, at once for a required check and at the daemon's next read of the runs
61
- (within two minutes) for a required workflow.
59
+ CI or a merge*: subscribe, then end the turn), never by a sleep loop.
60
+ A merge-group run is never re-run: the implementer finishes its round instead, and the pull request is tested again when it is queued again.
61
+ A completion while that red still stands is sent back, at once for a required check and at the daemon's next read of the runs (within two minutes) for a required workflow.
62
62
 
63
63
  A pull-request body edit re-runs a check that judges the body at once, on the head as it is. While
64
64
  the pull request conflicts with its base (GitHub shows it `CONFLICTING`), no workflow triggered
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sjawhar/claude-envoy",
3
- "version": "1.12.0",
3
+ "version": "1.12.1",
4
4
  "license": "Apache-2.0",
5
5
  "description": "Claude Code channel plugin for Legion's Envoy bus",
6
6
  "type": "module",