Skip to content

webcmd: v0.7.4

Latest

Choose a tag to compare

@github-actions github-actions released this 19 Aug 17:31
· 0 commits to b6560994e1a4fac3989ec0bcbb25b84e7790cec7 since this release
412c410

Improvements

  • Added structured -f/--format output to validate, verify, doctor, skills, daemon status, and profile list. Human-readable output remains the default.
  • Added effective -v/--verbose diagnostics for hosted commands, browser bridge commands, and auth status/auth refresh.
  • daemon status -f json now returns structured status data, including { "running": false } when the daemon is unavailable.
  • profile list -f json now returns connected profiles and saved aliases as structured rows.

Fixes

  • browser run compile errors now report the caller’s line and column, show a focused source excerpt with a caret, and provide clearer guidance for common quoting mistakes.
  • Browser sandbox responses and request bodies are now decoded correctly as UTF-8. Response.text(), Response.json(), Request.postData(), and page.request operations no longer produce comma-separated byte strings or fail JSON parsing.
  • Dead browser pages and contexts are now detected and replaced instead of being reused across subsequent browser run calls.
  • Opening a browser tab with a URL now honors waitUntil: none, avoiding hangs on pages that never reach the load event.
  • Built-in command failures now use the same structured error envelopes and exit codes as adapter commands instead of printing stack traces or surfacing unhandled rejections. Stack traces remain available with WEBCMD_DEBUG.
  • -f json now produces valid JSON error envelopes for local, adapter, and hosted command failures. Other formats continue to use YAML envelopes.
  • Unknown CLI flags now exit with usage code 2 and list the valid flags for the affected command.
  • validate <target> now rejects unknown sites or commands instead of reporting a zero-command pass. Validation failures also return a non-zero exit code.
  • profile use now rejects unknown profiles instead of saving an invalid default. Connected profiles, saved aliases, and the current default remain valid selections.
  • Non-interactive webcmd setup no longer prompts or hangs. Use --mode local, or --mode hosted --api-key <key>, when stdin is not a TTY.
  • Site-memory read-modify-write operations are now locked across processes, preventing concurrent note or endpoint updates from silently overwriting each other.
  • Concurrent downloads now use isolated temporary files. Pipeline items targeting the same destination are reported as conflicts instead of racing, corrupting, or overwriting files.
  • Ctrl-C cancellation now remains active for the full duration of asynchronous CLI operations.
  • Unknown browser subcommands now consistently exit with usage code 2.

Adapters

  • webcmd adapter override <site>/<command> now works in hosted mode, creating a tenant-private copy that can be edited with adapter source get and adapter source put.
  • Removed the undocumented webcmd browser fork alias. Calls now point users to webcmd adapter override <site>/<command>.
  • browser verify now accepts -f/--format, providing structured verification results including row counts, fixture status, memory checks, shape violations, fixture mismatches, and typed execution errors.
  • Corrected adapter override guidance to consistently use the <site>/<command> argument form.
  • The LinkedIn adapter now declares Webcmd >=0.7.4 as its minimum peer dependency.

Contributors

@Agnik47 @ankitranjan7 @beubax @Kaushik2003

@Agnik47 | @ankitranjan7 | @beubax | @Kaushik2003