Announcing External Dependencies
Spacelift Runs frequently rely on artifacts such as binaries or Docker images created during an earlier CI/CD step by systems like GitHub Actions. This reliance often led users to forgo using Push Policies, opting instead to initiate Spacelift runs via the API, a process that can become quite complex.With the introduction of External Dependencies, you can now define a set of dependencies within the push policy outcome that must be resolved before a run begins. Through the API, you simply mark these dependencies as completed (or failed), and any dependent runs will react accordingly.
