Repository navigation
ci: qualify SNP RustCrypto for upstream #243 - #1
Draft
mateo-moon wants to merge 12 commits into
Draft
mateo-moon wants to merge 12 commits into
mateo-moon wants to merge 12 commits into
Conversation
Signed-off-by: Jiale Zhang <zhangjiale@linux.alibaba.com>
Signed-off-by: Jiale Zhang <zhangjiale@linux.alibaba.com>
Signed-off-by: Jiale Zhang <zhangjiale@linux.alibaba.com>
Signed-off-by: Jiale Zhang <zhangjiale@linux.alibaba.com> (cherry picked from commit 6d14efb)
… compatibility Signed-off-by: Jiale Zhang <zhangjiale@linux.alibaba.com> (cherry picked from commit 964e6d7c8faacd404b67224d896265723b31c530)
Signed-off-by: Jiale Zhang <zhangjiale@linux.alibaba.com>
Signed-off-by: Jiale Zhang <zhangjiale@linux.alibaba.com> (cherry picked from commit d7a74be15b090cdaaaebcffef8aa9ac16b6f9d02)
Signed-off-by: Jiale Zhang <zhangjiale@linux.alibaba.com>
Signed-off-by: Jiale Zhang <zhangjiale@linux.alibaba.com> (cherry picked from commit f84a7c13230c31557fb32ebf72e9cf34647baecf)
Signed-off-by: Jiale Zhang <zhangjiale@linux.alibaba.com>
Bump the workspace reqwest dependency from 0.12 to 0.13, replacing the removed rustls-tls-native-roots feature with rustls: TLS roots now come from rustls-platform-verifier and webpki-roots is dropped. On native targets the rustls feature selects the aws-lc-rs provider; on wasm32 reqwest target-gates the whole rustls stack out and keeps the browser fetch backend, so aws-lc-rs is not compiled there. Bump artifact-resolve-sdk from e5ce195 to upstream main (8d65a85). The SDK's public API is unchanged; its only functional change is the same reqwest 0.12 to 0.13 bump, so the http_client() injection used by the AS policy-artifact-server tests stays on a single reqwest major and no renamed 0.12 alias is needed. The reqwest 0.11 and 0.12 entries still present in Cargo.lock come from the csv-rs and web3 git dependencies, not from workspace code. Assisted-by: Claude:glm-5.3
mateo-moon
force-pushed
the
codex/snp-rustcrypto-wasm
branch
from
November 2, 2026 10:13
2de4169 to
c873f70
Compare
Share SNP evidence, workload-binding and claim handling across the native OpenSSL and optional RustCrypto backends. Accept current CoCo evidence without changing the signed report bytes, and exercise both backends and WASM builds in CI.
mateo-moon
force-pushed
the
codex/snp-rustcrypto-wasm
branch
from
November 4, 2026 10:49
c873f70 to
95ee31d
Compare
This file contains hidden or 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
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.
Fork-side validation of openanolis/trustee#243, using the same
codex/snp-rustcrypto-wasmbranch and commit.All 18 PR-triggered CI jobs pass at
2de41693c4b40fbf8e86e20cba7a78817836b4bd:Confirmed failures fixed on the shared branch:
This draft PR stays open to track fork CI while upstream workflow approval is pending. One duplicate push-triggered RPM run was cancelled; the full PR-triggered RPM matrix passed.