v0.7.0

The deployed-commit check now works on deploy pipelines

Previously it only ever appeared on build pipelines. The reason is in the data: a build run carries a Git material with a real commit, while a deploy run's only material is a Pipeline dependency whose revision reads upstream-name/389/stage/1. There is no commit in a deploy run's build cause at all, so there was nothing to compare.

lazygocd now walks that dependency chain when a run has no Git material of its own, up to four hops with a cycle guard, and reports the commit it finds:

GitHub: acme/ui-app@release  25d63f5  up to date
        via my-app-lint-test-build #389

The via line makes clear the commit was inherited from upstream rather than read directly, so you are never misled about where it came from.

Deploy pipelines are exactly where "which commit is actually live?" matters most, so this closes the most useful gap in the feature.

brew upgrade lazygocd
cargo install lazygocd

Full Changelog: v0.6.1...v0.7.0