-
Notifications
You must be signed in to change notification settings - Fork 11.2k
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
chore(graphql): Align all e2e tests on protocol 51 #19402
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
3 Skipped Deployments
|
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.
I think the last protocol is 58/59, but I assume 51 works for now.
I'm just bringing all the tests in line at the same protocol version, not aiming to bump the protocol, which may introduce other unexpected changes. |
af40b5e
to
1940c09
Compare
306d002
to
09b977a
Compare
👍 |
## Description Some of these tests are on older versions because they landed around the time of the last bump. Bringing everything in line with protocol 51. ## Test plan ``` $ cargo nextest run -p sui-graphql-e2e-tests ```
09b977a
to
e6842ba
Compare
## Description Add `TransactionBlockFilter.affectedAddress` as a way to filter transactions by their relationship to an address without worrying about what kind of relationship that is. ## Test plan New E2E ## Stack - #19363 - #19371 - #19402 - #19403 --- ## Release notes Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required. For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates. - [ ] Protocol: - [ ] Nodes (Validators and Full nodes): - [ ] Indexer: - [ ] JSON-RPC: - [ ] GraphQL: - [ ] CLI: - [ ] Rust SDK: - [ ] REST API:
Description
Some of these tests are on older versions because they landed around the time of the last bump. Bringing everything in line with protocol 51.
Test plan
Stack
Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.