pullfrog 0.1.74 → 0.1.75

package/dist/internal.js

@@ -8,7 +8,7 @@ var __export = (target, all) => {
 // package.json
 var package_default = {
   name: "pullfrog",
-  version: "0.1.74",
+  version: "0.1.75",
   cliContractVersion: "1",
   type: "module",
   bin: {

package/dist/mcp/shell.d.ts

@@ -32,6 +32,11 @@ export declare function runSandboxed(params: {
     env: Record<string, string | undefined>;
     cwd: string;
     timeout: number;
+    /** live-stream chunks as they arrive, on top of the buffered `output`.
+     * lifecycle hooks use this to keep a long `pnpm test` visible in the
+     * workflow log instead of silent until it exits. */
+    onStdout?: (chunk: string) => void;
+    onStderr?: (chunk: string) => void;
 }): Promise<{
     output: string;
     exitCode: number;

package/dist/utils/lifecycle.d.ts

@@ -1,6 +1,19 @@
+import type { ShellPermission } from "../external.ts";
 export interface ExecuteLifecycleHookParams {
     event: string;
     script: string | null;
+    /**
+     * the repo's shell permission, which decides the hook's environment on the
+     * same terms as the `shell` tool: `enabled` inherits the full process env,
+     * anything else gets the default-deny allowlist (safe set + the repo's
+     * `envAllowlist`).
+     *
+     * hooks are maintainer-authored, but the code they invoke is not — after
+     * `checkout_pr` on a fork PR, a `prepushScript` of `pnpm test` runs the
+     * contributor's script and test files. so the hook is treated as untrusted
+     * execution and gets the same sandbox + env scrub as `shell`.
+     */
+    shell: ShellPermission;
     /**
      * when true, after the hook runs (success or failure), discard tracked-file
      * mods so the agent doesn't see hook-generated drift (e.g. `pnpm install`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pullfrog",
-  "version": "0.1.74",
+  "version": "0.1.75",
   "cliContractVersion": "1",
   "type": "module",
   "bin": {