v0.14.0

• documentation

  • a new step-by-step guide to testing a container image with dsyver, in docs/containers/testing-images.md: write a spec for an image, run it, read a failure, and put it in CI so it runs on every image build. The container image page now points to it

• the Docker wrappers

  • dsyver and the dgoss shim beside it gain SYVER_TEMP_DIR, so every variable they read now has a syver-named form. It pairs with DGOSS_TEMP_DIR rather than a GOSS_* name, because that variable is named after the script rather than the product and GOSS_TEMP_DIR has never existed. DGOSS_TEMP_DIR is still honoured, a non-empty SYVER_TEMP_DIR wins, and an exported-but-empty one cannot shadow it -- the same contract as every other pair
  • this fixes the macOS workflow the wrapper README already documented, which exports SYVER_TEMP_DIR and then runs dgoss. dgoss ignored the variable and fell back to /tmp, which is the private directory that example exists to work around
  • the wrapper's documentation now leads with the syver-named variables and spec filenames throughout. Every GOSS_* equivalent still works and goss.yaml is still read, so no existing setup needs changing

• dependencies

  • routine updates with no change to any check, flag or rendered output.
  • Go 1.26.8, up from 1.26.6, which brings the upstream fixes to net/http, behind serve and the http: check, and to the runtime and compiler
  • urfave/cli, the command line framework, moves to 3.13.0
  • gopsutil, which reads process and system information, to 4.26.9
  • prometheus/common, behind the prometheus output and /metrics, to 0.72.0
  • gomega, the matcher library behind every assertion, to 1.44.0
  • sprout, the template function library, moves to 1.1.2. Templated specs render as before