Version packages

@varlock/bumpy@1.14.1

Author: bumpy-bot

.bumpy/changelog-block-layout.md

@@ -1,5 +1,14 @@
 # Changelog
 
+## 1.14.1
+
+<sub>2026-06-18</sub>
+
+- [#118](https://github.com/dmno-dev/bumpy/pull/118) _(patch)_
+  Stream `buildCommand`/`publishCommand` output live to the parent process and surface the child's real failure reason. Custom publish commands (vsce, ovsx, anything bespoke) previously ran through a buffering runner that discarded stdout and never streamed output, so a failure like an expired marketplace token produced only a generic `Command failed` wrapper with no usable cause in CI logs. These commands now run through a streaming runner (`spawn` with piped+teed stdio) that prints output as it happens and includes both stdout and stderr in the thrown error. The capturing `runAsync`/`runArgsAsync` helpers (still used for internal git/npm calls whose output is parsed) also now include stdout in their error messages.
+- [#122](https://github.com/dmno-dev/bumpy/pull/122) _(patch)_
+  Changelog entries now use a block layout when a summary is multi-line, long (>120 chars), or contains markdown block syntax (headings, lists, blockquotes, code fences, tables). In those cases the entry metadata (`*(type)*`, PR link, "Thanks @user!") goes on its own line and the summary is rendered indented below it, instead of being jammed onto the same line. Short single-line summaries are unchanged and stay inline. Internal blank lines in a summary are now preserved so markdown paragraphs and lists render correctly. Applies to both the default and `github` formatters.
+
 ## 1.14.0
 
 <sub>2026-06-13</sub>

.bumpy/stream-custom-command-output.md

@@ -1,6 +1,6 @@
 {
   "name": "@varlock/bumpy",
-  "version": "1.14.0",
+  "version": "1.14.1",
   "description": "Modern monorepo versioning and changelog tool",
   "keywords": [
     "bump",