next-issue 2.5.5 → 2.5.7

package/README.md

@@ -476,8 +476,12 @@ The workflow then gives `next-issue` and `@ravshansbox/pi-next-issue` the same
 new version and publishes both packages to npm with a
 [trusted publish](https://docs.npmjs.com/trusted-publishers), so no token is
 stored. Only after the publish does it push the tag and make the GitHub release,
-so a failed publish leaves no half-release behind. A manual run of the workflow
-checks out the last tag and publishes that commit under the tag version, and
+so a failed publish leaves no half-release behind. npm makes a new version
+live a few minutes after the publish, and not always in the order it got them,
+so before it publishes, the job waits until npm serves both packages at the
+version of the last tag, for up to 10 minutes. Thus a new version never goes
+live before the one that came before it. A manual run of the workflow checks
+out the last tag and publishes that commit under the tag version, and
 changes nothing else. This repairs a release that reached GitHub but not npm.
 The release job stays on a GitHub runner, because npm takes provenance only
 from a GitHub runner.

package/dist/exec.mjs

@@ -1,6 +1,8 @@
+import { AsyncLocalStorage } from 'node:async_hooks';
 import { spawn } from 'node:child_process';
 let observer;
-let defaultTimeoutMs = 10 * 60_000;
+const DEFAULT_TIMEOUT_MS = 10 * 60_000;
+const defaultTimeout = new AsyncLocalStorage();
 const STDERR_TAIL = 200_000;
 const groups = new Set();
 const stoppers = new Set();
@@ -50,12 +52,12 @@ export function track(child) {
 export function setCommandObserver(next) {
     observer = next;
 }
-export function setDefaultTimeout(ms) {
-    defaultTimeoutMs = ms;
+export function withDefaultTimeout(ms, body) {
+    return defaultTimeout.run(ms, body);
 }
 export function run(command, args, options = {}) {
     const started = Date.now();
-    const limit = options.timeoutMs ?? defaultTimeoutMs;
+    const limit = options.timeoutMs ?? defaultTimeout.getStore() ?? DEFAULT_TIMEOUT_MS;
     return new Promise((resolve, reject) => {
         const child = spawn(command, args, {
             cwd: options.cwd,

package/dist/run.mjs

@@ -2,7 +2,7 @@ import { AsyncLocalStorage } from 'node:async_hooks';
 import { writeFile } from 'node:fs/promises';
 import { join } from 'node:path';
 import { loadConfig } from './config.mjs';
-import { setCommandObserver, setDefaultTimeout } from './exec.mjs';
+import { setCommandObserver, withDefaultTimeout } from './exec.mjs';
 import { detectRepo } from './git.mjs';
 import { defaultBranch } from './github.mjs';
 import { exitCode, runIssues, watchIssues } from './loop.mjs';
@@ -25,7 +25,9 @@ export function recordCommands(recorder, work) {
 }
 export async function runRepo(root, args, controls) {
     const config = await loadConfig(root);
-    setDefaultTimeout(config.commandTimeoutMinutes * 60_000);
+    return withDefaultTimeout(config.commandTimeoutMinutes * 60_000, () => runWithConfig(root, args, controls, config));
+}
+async function runWithConfig(root, args, controls, config) {
     const repo = await detectRepo(root, config.remote);
     const recorder = await Recorder.create(repo.root, args.level, controls.onEvent);
     const pruned = await pruneRuns(repo.root, config.keepRunDays);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "next-issue",
-  "version": "2.5.5",
+  "version": "2.5.7",
   "description": "Autonomous issue harness driven by the pi SDK",
   "keywords": [
     "github",