Skip to content

Version Packages#82

Open
github-actions[bot] wants to merge 1 commit intomainfrom
changeset-release/main
Open

Version Packages#82
github-actions[bot] wants to merge 1 commit intomainfrom
changeset-release/main

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions Bot commented May 4, 2026

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@generata/core@1.3.0

Minor Changes

  • 66b0511: Programmatic runWorkflow / runAgent now write prompt logs to the same <logsDir>/<kind>/<name>-<runId>.log paths the CLI uses, mirroring the CLI's logPrompts flow. The path is printed once to stderr at run start as Full log: file:///... so callers can click through and tail the file as it streams - this fires for both CLI and programmatic runs, with or without onEvent. Pass promptLogFile to override the path.

    Silent-mode programmatic runs also print a header to stderr: workflow: <name> (<n> steps) or agent: <name> [<type>]. Suppressed when onEvent is wired (the caller is driving display).

    Auto-derived programmatic log paths now prepend the calling script's basename - e.g. logs/workflow/batch-script-review-note-<runId>.log instead of logs/workflow/review-note-<runId>.log - so logs from different scripts driving the same workflow are easy to tell apart. CLI runs and explicit promptLogFile overrides are unaffected.

    consoleSink no longer prints the prompt log path itself on workflow-start / agent-welcome - runWorkflow / runAgent are now the single source for that line.

    The logPrompts config default has flipped from false to true - prompt logs are on by default for both CLI and programmatic runs. Set logPrompts: false in generata.config.ts to opt out.

  • 18264a7: Expose runWorkflow and runAgent as public API so workflows and agents can be driven from code. Programmatic callers run silently by default and subscribe to structured EngineEvents via onEvent. The CLI is unchanged in behaviour.

    AbortSignal is now wired through runWorkflow end-to-end: a pre-aborted signal short-circuits before precheck/worktree setup, and a signal that fires mid-step bypasses the per-agent retry loop and propagates AbortError to the caller.

    The EngineEvent union now emits a discrete halt event when a worker calls emit --halt, and workflow-start carries the runId (the same id stamped into per-step metric records) so subscribers can correlate events with metrics.

    One internal-behaviour change worth flagging: critic-step max-retries no longer throws inside the engine. The CLI now exits non-zero by checking result.success. Same observable outcome for end users; loop-friendly contract for programmatic callers.

  • 27e4f47: worktree({...}) now accepts a cleanup field (default false). When false, the worktree and its generata/wt-<runId> branch are kept on disk after the workflow finishes so you can inspect the run; pass cleanup: true to restore the previous teardown-on-exit behaviour. The engine logs [worktree] cleaned up <path> or [worktree] preserved at <path> at end of run. Setup-failure cleanup is unchanged - half-built worktrees are still torn down. Use generata worktree prune to clear preserved worktrees.

  • b9d8165: Fix worktree isolation prompt header and surface typed outputs on WorkflowResult.

    The prompt's Working directory: line (and the agent factory's ${work_dir} substitution) now reflect the actual cwd the agent runs in, not the user-config workDir. Agents under worktree isolation were previously misled into resolving absolute file paths against the main repo and mutating it instead of the worktree.

    WorkflowResult now exposes outputs: Record<string, string> (typed outputs accumulated across steps) and worktreePath?: string (when the workflow ran with worktree isolation), so programmatic post-workflow drivers can read what agents emitted and locate the worktree without re-deriving either.

Patch Changes

  • 5613d29: Capture kill reason and signal in agent metrics. When a timeout fires the runner records killReason, the OS signal, and any abnormal close-delay in metrics.error, and sets status: "timeout". Previously a SIGTERM kill left only the benign "no stdin data received in 3s" warning and a generic "failure" status, making it impossible to distinguish timeout from crash.
  • 5f32d49: Deduplicate build and prepare scripts. Set prepare to call pnpm build so future changes to the build process happen in one place.
  • 6a2000b: Dedupe metrics printing in the CLI. Internal refactor that extracts a printSummary helper so the today/week/agent metrics commands share one formatter; output is unchanged.
  • 2686c7b: Drop the generata ASCII banner and randomised tagline from the start of generata agent and generata workflow runs. The workflow start header (name, isolation, prompt log) is now the first thing printed. Removes the logBanner and pickWorkflowTagline exports from @generata/core/logger.
  • a40de4d: refactor(core): extract template install defaults to shared utility
  • 513d89d: Prevent shell injection in macOS notifications by using execFileSync instead of string interpolation.
  • a7c5edd: Fix preflight uses platform-specific command lookup. Use where on Windows and which on Unix-like systems to properly detect CLI tools on all platforms.
  • 44618b5: Expand templates README with typed-output workflow example. Documents how typed outputs flow between workflow steps with full type safety.
  • 6ebd0a0: Skip .DS_Store files when copying templates during project initialization, preventing macOS metadata files from being included in user projects.
  • 1d9a076: setupWorktree's cleanup now probes the throwaway branch with git rev-parse --verify before issuing git branch -D. Skipping the delete when the branch is gone keeps cleanup quiet for callers (e.g. shippers) that have renamed the worktree branch to a semantic name and pushed it.
  • a59ee2f: setupWorktree no longer wraps git fetch, git worktree add, and the install command in animated spinners. Each step now prints a plain → worktree: ... line instead. The spinners often appeared frozen on fast operations because the work completed before the animation could cycle, and the cursor blinking on top of the braille frames read as buggy.

@generata/self-improve@0.0.2

Patch Changes

@github-actions github-actions Bot force-pushed the changeset-release/main branch 17 times, most recently from 515d915 to b03fcc6 Compare May 8, 2026 10:25
@github-actions github-actions Bot force-pushed the changeset-release/main branch from b03fcc6 to 9cc2f49 Compare May 8, 2026 11:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants