v0.3.3

v0.3.3

Report portability

• Remove the undeclared remote mktemp dependency from read-only report
  collection.
• Build the remote include list with POSIX shell positional parameters and
  stream the existing scopes directly through GNU tar.
• Preserve valid empty remote snapshots without creating a temporary file on
  the managed host.

Validation coverage

• Add a unit regression for the generated remote tar script.
• Run the SSH report end to end with mktemp deliberately unavailable on the
  remote server.
• Exercise that regression on GNU tar 1.34, GNU tar 1.35, and the packaged PEX
  path.

Operational impact

• Hosts accepted by doctor no longer need an additional mktemp command to
  run a report.
• The CLI, configuration schema, archive format, and report schema are
  unchanged.

v0.3.2

v0.3.2

Compatibility

• Qualify GNU tar 1.35 for the remote capability contract used by doctor,
  alongside the existing GNU tar 1.34 qualification.
• Keep the compatibility decision based on an exact tested-version allowlist:
  later GNU tar versions remain undetermined until they are explicitly
  qualified.

Validation coverage

• Run the complete SSH end-to-end suite against Debian Bookworm with GNU tar
  1.34 and Debian Trixie with GNU tar 1.35.
• Run the packaged PEX end-to-end suite and the local GitHub Action smoke test
  against GNU tar 1.35.
• Keep dedicated mise tasks for each qualified environment and retain the
  aggregate test:e2e task as the entry point for both suites.

Operational impact

• Managed servers reporting GNU tar 1.35 can now receive a compatible
  verdict when all required commands and tar options are available.
• The CLI, configuration schema, archive format, and GNU tar 1.34 support are
  unchanged.

v0.3.1

Security

• Pin every external GitHub Action used by the composite action and repository
  workflows to an immutable commit while retaining version comments for
  maintainable updates.
• Enforce full commit pinning for future workflow and composite-action changes
  with zizmor in the standard project checks.

Release process

• Require substantive, versioned release notes to be committed and validated
  before a GitHub Release is created.

Compatibility

• This patch does not change the CLI, configuration version, archive format, or
  supported Linux x86_64 runtime.

v0.3.0

Release v0.3.0

v0.2.5

Release v0.2.5

v0.2.3

Release v0.2.3

v0.2.2

Release v0.2.2