-
Notifications
You must be signed in to change notification settings - Fork 327
OPDATA-3845: Decouple proof-of-reserves from dependencies #4279
New issue
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
Conversation
🦋 Changeset detectedLatest commit: 49c7a49 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
mxiao-cll
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need to be careful releasing this one, can you also include some sample requests that you've tested locally?
|
I'll do it Thursday next week. |
I've tried the 54 requests from live feeds in RDD that use |
OPDATA-3845
Description
proof-of-reservesdepends on a lot of other adapters.This means that if any of those adapters get released,
proof-of-reservesmust be released as well.The dependencies only exist to refer to the names of these adapters.
Changes
devDependencies.Steps to Test
yarn test packages/composites/proof-of-reserves/test/unit/adapter-names.test.tsada-balanceand then a release and checked thatproof-of-reserveswas not included.Quality Assurance
infra-k8sconfiguration file.adapter-secretsconfiguration file or update the soak testing blacklist.test-payload.jsonfile with relevant requests.feature/x,chore/x,release/x,hotfix/x,fix/x) or is created from Jira.