chore(deps): bump a3p proposals synthetic-chain to 0.3.0 #10215
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
turadg
approved these changes
Oct 7, 2024
Jorge-Lopes
force-pushed
the
jorge/acceptance-synthetic-chain-version
branch
from
b5cf42a to
65b293f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
closes: https://github.com/Agoric/BytePitchPartnerEng/issues/11
Description
This PR intend to update the
agoric/synthetic-chainpackage of the a3p-integration proposals to the same version as it is declared on thea3p-integration rootwhich isv^0.3.0, providing the tests with the most recent tools.The proposals affected by the update was:
^0.1.0to^0.3.0^0.1.0to^0.3.0^0.2.1to^0.3.0Note: this PR required the verification that this versions was not intentionally held back by the Agoric team for specific reasons.
Security Considerations
No security considerations were identified.
Scaling Considerations
No scaling considerations were identified.
Documentation Considerations
No documentation considerations were identified.
Testing Considerations
All tests from the 3 proposals were run locally after updating the version, and they passed with expected behavior. No additional tests should be required beyond the unit tests currently in place.
Upgrade Considerations
No upgrade considerations were identified.