Repository navigation
Conversation
utoipa goes from 3.5.0 to 6.0.0. Guardian's Integrity Service embeds these models in its OpenAPI document, and it can only reach a zip without CVE-2026-115905 through utoipa-swagger-ui 10, which needs utoipa 6. The two hex-encoded hash fields keep `type: string, format: binary`: utoipa 6 would otherwise describe a `[u8; N]` as an array of integers, which isn't what serde writes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
captjt
requested review from
TJbrunk,
bsayed,
cameronfyfe,
luke-moss-dev and
tmccoy14
October 29, 2026 13:26
luke-moss-dev
approved these changes
Oct 29, 2026
bsayed
approved these changes
Oct 29, 2026
cameronfyfe
approved these changes
Oct 29, 2026
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.
Part of GRD-270.
Guardian's Source Scan fails on CVE-2026-115905 (
zip< 9.0.5). Guardian's Integrity Service getszip0.6.6 only as a build dependency ofutoipa-swagger-ui3. Onlyutoipa-swagger-ui10 uses a fixedzip, and it needs utoipa 6. The Integrity Service embeds about 25 of these models in its OpenAPI document, so the models have to move first: utoipa 6 can't use utoipa 3 derives.integrity-lineage-models:utoipagoes from 3.5.0 to 6.0.0, with the same features. It's the only crate here that uses utoipa. The lockfile addsutoipa-gen6.0.1 and itssyn3.UrnCidWithSha256.sha256andUrnCidWithSha384.sha384are[u8; N]written as hex strings. utoipa 6 would describe them as arrays of integers, so#[schema(value_type = String, format = Binary)]keeps the schema they had.Unreleasedentry, marked Breaking: because theToSchemaimpls are now utoipa 6's. Serialization and the Rust API are unchanged.Schema comparison
I dumped every
ToSchematype's schema under utoipa 3 (main) and utoipa 6 (this branch). Then I compared them after mapping OpenAPI 3.0'snullable: trueonto 3.1's"null"type member. What's left:$refs, and maps declarepropertyNames: {type: string}.anchor::Locationloses itsdiscriminator: {propertyName: type}: utoipa 6 only derives discriminators for untagged enums. EachoneOfarm still requires itstypevalue, so the JSON it accepts is the same. The Integrity Service's published spec never carried this discriminator, because a service type namedLocationreplaces it there.ValueOrArray<String>: it pointed at a non-existentTschema and now points atString. Nothing references it, becauseComputationStatement.inputandoutputoverride it withvalue_type = String.Checks
These pass on Rust 1.94.1 in
nix develop:just ci: fmt-check, readme-check, build, build-wasm, lint, lint-docs, test (90 passed), test-wasmcargo check --locked -p integrity-ffi --features blob-all,signer-allAfter merging: Guardian needs a
v0.0.21release to pick this up. The Guardian side is the axum 0.8 / utoipa 6 move in the Integrity Service.🤖 Generated with Claude Code