github.com/mfridman/tparse

What's changed

• Wrap panic messages at the terminal width (#142)
• Do not include packages with no coverage in the output (#144)

New Contributors

• @masaru-iritani made their first contribution in #142
• @BrunoKrugel made their first contribution in #144

Full Changelog: v0.17.0...v0.18.0

• Wrap panic messages at the terminal width (#142)
• Do not include packages with no coverage in the output (#144)

This tag was signed with the committer’s verified signature .

mfridman Michael Fridman

SSH Key Fingerprint: eZwhISKBUqae5UnixEND7un7fgr/uigRwTfPA/EwZbo Verified Learn about vigilant mode .

ba2512e

This commit was signed with the committer’s verified signature .

mfridman Michael Fridman

SSH Key Fingerprint: eZwhISKBUqae5UnixEND7un7fgr/uigRwTfPA/EwZbo Verified Learn about vigilant mode .

What's changed

• Wrap panic messages at the terminal width ( #142 )

• Do not include packages with no coverage in the output ( #144 )

New Contributors

• @masaru-iritani made their first contribution in #142

• @BrunoKrugel made their first contribution in #144

Full Changelog : v0.17.0...v0.18.0

Contributors

masaru-iritani and BrunoKrugel

What's changed

• Deprecate github.com/mfridman/buildversion, and use std lib debug.ReadBuildInfo() instead. In
  go1.24 this is handled automatically, from the release notes:

  The go build command now sets the main module’s version in the compiled binary based on the
  version control system tag and/or commit. A +dirty suffix will be appended if there are
  uncommitted changes. Use the -buildvcs=false flag to omit version control information from the
  binary.

• Handle changes in go1.24 related to build output. tparse will pipe the build output to stderr
  (maintaining similar behavior as pre-go1.24)

  Furthermore, go test -json now reports build output and failures in JSON, interleaved with
  test result JSON. These are distinguished by new Action types, but if they cause problems in a
  test integration system, you can revert to the text build output with GODEBUG setting
  gotestjsonbuildtext=1.

What's changed

• Add a -follow-output flag to allow writing go test output directly into a file. This will be
  useful (especially in CI jobs) for outputting overly verbose testing output into a file instead of
  the standard stream. (#134)

  flag combination	go test output destination
  No flags	Discard output
  -follow	Write to stdout
  -follow-output	Write to file
  -follow -follow-output	Write to file

• Use charmbracelet/lipgloss for table rendering.
  • This will allow for more control over the output and potentially more features in the future.
    (#136)
  • Minor changes to the output format are expected, but the overall content should remain the same.
    If you have any feedback, please let me know.

What's changed

• Add -trimpath flag, which removes the path prefix from package names in the output, simplifying
  their display. See #128 for examples.
  • There's a special case for -trimpath=auto which will automatically determine the prefix based
    on the longest common prefix of all package paths.

What's changed

• Modify --follow behavior by minimizing noisy output. (#122)

What's changed

• General housekeeping and dependency updates.

What's changed

• Add partial support for -compare. A feature that displays the coverage difference against a previous run.
  • See description for more details #101 (comment) and the initial issue #92.
• Fix unstable common package prefix logic #104

What's changed

• Fix failing GoReleaser github action (release notes location).

Summary from v0.13.0

• Start a CHANGELOG.md for user-facing change.
• Add GoReleaser to automate the release process. Pre-built binaries are
  available for each release, currently Linux and macOS. If there is demand, can also add Windows.

• Fix failing GoReleaser GitHub action (release notes location).

Summary from v0.13.0

• Start a CHANGELOG.md for user-facing change.
• Add GoReleaser to automate the release process. Pre-built binaries are available for each release, currently Linux and macOS. If there is demand, can also add Windows.

• Start a CHANGELOG.md for user-facing change.
• Add GoReleaser to automate the release process. Pre-built binaries are available for each release, currently Linux and macOS. If there is demand, can also add Windows.

What's Changed

• Record the start event with the package start time. #94
• Shorten package name only for -smallscreen. #96

This version also bumps the minimum Go version to v1.17 and upgrades all the dependencies.

The release binaries have been temporarily disabled, so, for now, you'll need to go install the tool, example:

$ go install github.com/mfridman/tparse@latest       
go: downloading github.com/mfridman/tparse v0.12.2

Full Changelog: v0.12.1...v0.12.2