Run dependent (such as Agoric SDK) integration tests against Endo as it changes. This would shift the burden of compatibility and drift onto the shoulders of PR authors, rather than having to bite the bullet every time we discover incompatibilities and address them with broad changes like #1759.
Description of the Design
It would likely consist of a webhook that somehow activates the dependent repository's CI, but we need to have a narrow credential scope so that no privileges are leaked into the Endo CI flow.
Security Considerations
Needs more design.
Scaling Considerations
Probably cannot be part of the PR flow, or it could take too long to run.
What is the Problem Being Solved?
Run dependent (such as Agoric SDK) integration tests against Endo as it changes. This would shift the burden of compatibility and drift onto the shoulders of PR authors, rather than having to bite the bullet every time we discover incompatibilities and address them with broad changes like #1759.
Description of the Design
It would likely consist of a webhook that somehow activates the dependent repository's CI, but we need to have a narrow credential scope so that no privileges are leaked into the Endo CI flow.
Security Considerations
Needs more design.
Scaling Considerations
Probably cannot be part of the PR flow, or it could take too long to run.
Test Plan
Upgrade Considerations