We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Our docker-based upgrade-tests are our only way in CI to verify that new proposals against (approximate) Mainnet will succeed.
upgrade-tests
Partner proposals (outside agoric-sdk) change Mainnet too and must be included in the history.
Some way for agoric-sdk to fetch manifests and bundles from partner proposals.
And/or a new repo outside of agoric-sdk that tests chain upgrades against a history.
The text was updated successfully, but these errors were encountered:
@turadg and I plan to land this in a separate repo (#8443)
Sorry, something went wrong.
The agoric-3-proposals design seems to suffice; we have 2 CoreEval proposals working:
dckc
Successfully merging a pull request may close this issue.
What is the Problem Being Solved?
Our docker-based
upgrade-tests
are our only way in CI to verify that new proposals against (approximate) Mainnet will succeed.Partner proposals (outside agoric-sdk) change Mainnet too and must be included in the history.
Description of the Design
Some way for agoric-sdk to fetch manifests and bundles from partner proposals.
And/or a new repo outside of agoric-sdk that tests chain upgrades against a history.
Security Considerations
Scaling Considerations
Test Plan
Upgrade Considerations
The text was updated successfully, but these errors were encountered: