[kvid]

Unfortunately, the v0.5 is still not close to finished, and I therefore in the meantime prepare a small release by collecting into this branch some PRs with bug-fixes and other small changes that should be easy to merge into the v0.5-dev branch later.

• Add optional tweak per node with name placeholder #357 - if approved
• Create issue templates #387
• Add SVG Mime Type #443
• Fix template search path #473 + suggested generalization on top
• Handle different color specifiers #495
• Avoid string operation on a None gauge_unit value #498
• Add gauge_equiv options #499 - if approved
• Add example projects to docs #501 (currently unavailable due to a system error)
• Print more information when repeating -V option #507 - if finalized and approved
• Write diagnostic messages to stderr #512
• Add __main__.py to support python -m wireviz #513
• TODO: Any other candidates?

[martinrieder]

• TODO: Any other candidates?

@SomethingNew71 proposed some contributions from his fork at ClassicMiniDIY/WireViz in #316 (comment)

So far I've merged in #321, #234, #367, #444, #379, #357, #492, #496, #495, #473 and #443, added tests, and fixed around 20 bugs (#497 and #510 included). That's all in v1.0.0. Still GPLv3, it's based on master (not dev), and each commit links back to the original PR or issue.

The fork used these existing upstream PRs as the foundation, so we might consider cross-checking and adding some of them. I added checkmarks for easier comparison with the list above:

• Pull in 4 bug fixes from upstream wireviz/WireViz ClassicMiniDIY/WireViz#1
  • Add SVG Mime Type #443
  • Fix template search path #473
  • Handle different color specifiers #495
  • Fix loopback rendering (issue #439) #496
• Ship stdin/stdout + 6 feature ports to master ClassicMiniDIY/WireViz#10
  • Add stdin/stdout streaming (port of upstream PR #321) ClassicMiniDIY/WireViz#2
    • resolves #320 read from stdin and write to stdout #321
  • Bring 6 upstream PR ports onto upstream-fixes ClassicMiniDIY/WireViz#9
    • Add support for a custom template directory path #444
    • Added option to set the dpi of the output #379
    • Embed YAML data into PNG #234
    • Added <!-- %revision% --> place-holder #492
    • Add optional tweak per node with name placeholder #357
    • Complete PDF output handler #367

Some of the following bugfixes come additional, but they do not have an upstream issue or PR to be listed here anyway:

• Add comprehensive pytest suite (134 tests) + fix 3 bugs it found ClassicMiniDIY/WireViz#11

  Adds an automated pytest test suite covering the entire WireViz API surface. 134 tests across 9 files, [...] surfacing three real bugs, all fixed in this same PR.

  May 2026: Fixed 3 bugs discovered in testing and 5 bugs from previous integration (ClassicMiniDIY@e4f485e)

• WireViz 1.0.0 — security hardening, audit bug fixes, Python 3.9+ ClassicMiniDIY/WireViz#12

  Security hardening and bug fixes from the October 2026 audit. First stable release of the fork. Design and threat model: 026-10-02-october-2026-audit.md

  • Included Avoid string operation on a None gauge_unit value #498 fixing #497
  • Bugfix for Pin labels work in cable connections but raise ValueError in arrow (mate) connections #510 contained in ClassicMiniDIY@3bbc859

Many more changes were applied in additional batches, each covering multiple issues at once. These would need to be broken down into smaller pieces for reviewability. See 2026-10-02-upstream-issue-triage.md and 2026-10-02-batch-c-design.md for details.

• fix: upstream bug batch A + security hardening ClassicMiniDIY/WireViz#14
• feat: upstream feature batch B — CSV BOM, loop colors, images, terminology ClassicMiniDIY/WireViz#15
• feat: upstream batch C — include, twisted pairs, shorts, sheet PDF, errors ClassicMiniDIY/WireViz#16

[ggrossetie]

Hi @kvid,

Regarding "Any other candidates?", I'd like to propose three small PRs, all based on master and mergeable without conflicts:

• Write diagnostic messages to stderr #512 Write diagnostic messages to stderr
• Add __main__.py to support python -m wireviz #513 Add __main__.py to support python -m wireviz
• resolves #320 read from stdin and write to stdout #321 Read from stdin and write to stdout (resolves [feature] Read from stdin and write output (PNG, SVG) to stdout #320), stacked on Write diagnostic messages to stderr #512

Some context: WireViz is one of the diagram libraries available on Kroki, which renders diagrams from textual descriptions over HTTP. Kroki pipes the YAML into WireViz and reads the SVG back from stdout. Since this isn't supported upstream, we've been maintaining a fork (yuzutech/WireViz) since 2023, still based on v0.3.2. Getting these changes into v0.4.2 would allow us to drop the fork and offer an up-to-date WireViz to Kroki users.

The changes are limited to the CLI and print calls: the library API and the generated files are unchanged. Since wv_cli.py is nearly identical on dev, they should also be easy to port to v0.5 later. I rewrote #321 from scratch on top of master for this purpose; the previous dev-based version was much larger. As mentioned above, an earlier version of #321 is also included in ClassicMiniDIY/WireViz, so it seems other users need it too.

I'm happy to address any feedback, or to rebase onto release/v0.4.2-rc if you prefer.

[martinrieder]

@ggrossetie No doubt that #513 qualifies for this bugfix release, but I think that changing the output stream in #321 and #512 are significant changes. The latter should rather be in 0.5, but anyway I vote for this when it improves error detection for nanangp/vscode-wireviz-preview#7, which would work even better with this:

• Improve error messages for YAML validation failures #506

Additionally we could add some documentation or template fixes without risk:

• added a tutorial (tutorial09) #454
• Clarify and align SYNTAX and README descriptions #406

Also I suggest to cherry-pick 22c5250 that was suggested here:

• Added <!-- %revision% --> place-holder #492

[ggrossetie]

Thanks @martinrieder for taking the time to consider my changes for this release.

Fair point. I agree #321 is a larger change (it also touches the Python API, e.g. generate_html_output and embed_svg_images_file), so it makes sense to target 0.5.

#512 is much narrower: generated files are unchanged, only diagnostic messages move from stdout to stderr. The only consumers affected would be tools parsing stdout to capture warnings, and they get a cleaner contract in return (stdout for output, stderr for diagnostics), which is exactly what helps nanangp/vscode-wireviz-preview#7. Since we're still in 0.x, I think it's acceptable in 0.4.2 as long as it's called out explicitly in the CHANGELOG, something like:

"Breaking: warnings and progress messages are now written to stderr instead of stdout. If you were capturing them from stdout, read stderr instead. wireviz -V still prints to stdout."