1.5.0 – Workflow configuration checks + injectable prompt for non-interactive automation

Main changes

Workflow configuration introspection (new)

This release adds checkWorkflowConfiguration(), which inspects a repository’s GitHub Actions workflows and reports whether they appear to trigger on pull requests to a given target branch.

Why this matters:

• Helps automation detect “why am I not seeing PR checks?” situations earlier (e.g., workflows exist but don’t run on pull_request, or branch filters don’t match).
• Provides structured output you can surface in CLI/CI logs (workflow count, which workflows would trigger, and an optional warning).

Injectable confirmation prompt (new)

Interactive decisions in GitHub operations can now be controlled via an injectable prompt function:

• setPromptFunction(fn) allows consumers (CLIs, CI jobs, UIs) to control confirmation behavior.
• A default prompt implementation is provided for non-interactive environments (defaults to YES).

Why this matters:

• Enables fully non-interactive release/merge automation without brittle stdin hacks.
• Lets tools provide consistent UX (e.g., your own CLI prompt library) while reusing @grunnverk/github-tools logic.

Other updates

Package/dependency and build metadata refresh

• Package metadata and build configuration were updated as part of the release prep.
• Dependency versions were refreshed (notably aligning with the @grunnverk/git-tools 1.5.x line).

Documentation updates

• README and the agent guide were refreshed to reflect current capabilities and usage patterns.

Breaking changes

No breaking changes were detected in the main → HEAD range. If you rely on documentation snippets as copy/paste examples, review them against the exported API in src/index.ts to ensure you’re using the currently exported function names/signatures.