-
Notifications
You must be signed in to change notification settings - Fork 11.3k
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
WIP DNM: Joy/move attestation #20859
Closed
Closed
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
The latest updates on your projects. Learn more about Vercel for Git ↗︎
2 Skipped Deployments
|
joyqvq
temporarily deployed
to
sui-typescript-aws-kms-test-env
January 10, 2025 20:20 — with
GitHub Actions
Inactive
joyqvq
force-pushed
the
joy/move-attestation
branch
from
January 10, 2025 20:45
a39e06d
to
6a4fe2e
Compare
joyqvq
temporarily deployed
to
sui-typescript-aws-kms-test-env
January 10, 2025 20:46 — with
GitHub Actions
Inactive
joyqvq
force-pushed
the
joy/move-attestation
branch
from
January 10, 2025 20:49
6a4fe2e
to
5f14b17
Compare
joyqvq
temporarily deployed
to
sui-typescript-aws-kms-test-env
January 10, 2025 20:49 — with
GitHub Actions
Inactive
joyqvq
force-pushed
the
joy/move-attestation
branch
from
January 10, 2025 22:16
5f14b17
to
8052c8d
Compare
joyqvq
temporarily deployed
to
sui-typescript-aws-kms-test-env
January 10, 2025 22:16 — with
GitHub Actions
Inactive
joyqvq
force-pushed
the
joy/move-attestation
branch
from
January 11, 2025 03:49
8052c8d
to
e9237cb
Compare
joyqvq
temporarily deployed
to
sui-typescript-aws-kms-test-env
January 11, 2025 03:49 — with
GitHub Actions
Inactive
joyqvq
force-pushed
the
joy/move-attestation
branch
from
January 13, 2025 15:17
e9237cb
to
e9d8e0a
Compare
joyqvq
temporarily deployed
to
sui-typescript-aws-kms-test-env
January 13, 2025 15:17 — with
GitHub Actions
Inactive
joyqvq
force-pushed
the
joy/move-attestation
branch
from
January 13, 2025 19:48
e9d8e0a
to
f4ba9cb
Compare
joyqvq
temporarily deployed
to
sui-typescript-aws-kms-test-env
January 13, 2025 19:48 — with
GitHub Actions
Inactive
joyqvq
temporarily deployed
to
sui-typescript-aws-kms-test-env
January 13, 2025 21:39 — with
GitHub Actions
Inactive
joyqvq
force-pushed
the
joy/move-attestation
branch
from
January 13, 2025 22:15
9116522
to
55e7db4
Compare
joyqvq
temporarily deployed
to
sui-typescript-aws-kms-test-env
January 13, 2025 22:15 — with
GitHub Actions
Inactive
joyqvq
temporarily deployed
to
sui-typescript-aws-kms-test-env
January 13, 2025 22:17 — with
GitHub Actions
Inactive
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.
Description
included in https://github.com/MystenLabs/sui/blob/03aba9d6e5c17d04d5d8acefda80a5392c2091cb/sui-execution/v1/sui-move-natives/Cargo.toml for a different version of x509-parser (as opposed to 0.14 used by sui-types in sui-execution/latest) compiles ok.
Test plan
How did you test the new or updated feature?
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.