@stackline/git-diff-tree 1.0.1

@stackline/git-diff-tree@1.0.1

Independent Stackline maintenance fork. Original authors and licenses are retained.

Source commit: 2324d7f
Publication: https://github.com/alexandroit/stackline-git-diff-tree/actions/runs/36506641214/attempts/1
CI: https://github.com/alexandroit/stackline-git-diff-tree/actions/runs/36506505675

The published tarball is the exact artifact tested in CI. Registry bytes, provenance,
signatures, direct and aliased installs, and zero known production audit findings were verified.
Audit results are a point-in-time check, not a guarantee of absolute security.

See the repository changelog and notices for the focused fixes and upstream attribution.

@stackline/git-diff-tree 1.0.3

Documentation and package discovery update for @stackline/git-diff-tree@1.0.3.

Uses the published 1.0.1 tarball as the baseline. Only the README and package version, keywords and homepage changed. All other 9 file contents are identical; runtime/development dependencies, original authors and license are preserved.

Documentation · Publication evidence

SHA-512: 2da960405fef824e96ce408cde8d86967cdbe5e83de22f97d9454ea9505936f5315600b82a5cc0c649dc8bf6c38eb28978fe2466fb7fbc87a0a2239e7d66c4ae

@stackline/git-diff-tree 1.0.2

Historical documentation-only publication, superseded by @stackline/git-diff-tree@1.0.3. Runtime files and dependency requirements are unchanged from 1.0.1. Original authors and licenses remain preserved.

Original GitHub Actions publication

SHA-512: f8d019f36c0006b5378f493482e16b2a165a13081590fa08d0b9849b78bd6bc2bfb71da6d487562c4d2828d83a9d70b3967931e1dbd1eaa9bad151326781110d

@stackline/git-diff-tree 1.0.0

@stackline/git-diff-tree@1.0.0

Independent Stackline maintenance fork. Original authors and licenses are retained.

Source commit: 47f2de0
Publication: https://github.com/alexandroit/stackline-git-diff-tree/actions/runs/36334895495/attempts/1
CI: https://github.com/alexandroit/stackline-git-diff-tree/actions/runs/36335137796

The published tarball is the exact artifact tested in CI. Registry bytes, provenance,
signatures, direct and aliased installs, and zero known production audit findings were verified.
Audit results are a point-in-time check, not a guarantee of absolute security.

See the repository changelog and notices for the focused fixes and upstream attribution.