Repository navigation
verify-ml-dsa-provider-documents - #23
Merged
Merged
Conversation
This was referenced Oct 23, 2026
Add opt-in shared ML-DSA-65 document verification to registry/catalog reads, references and facade plans. Isolate verified reads from unverified parse caches. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
jeffreyaven
force-pushed
the
feature/ml-dsa-provider-signatures
branch
from
October 24, 2026 01:35
412bd23 to
f510d0c
Compare
general-kroll-4-life
approved these changes
Oct 24, 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.
Summary
stackqldoc.WithVerifierusing the shared FIPS 204 ML-DSA-65 package from ml-dsa-provider-signatures stackql/stackql-provider-registry#487.Args.DocumentVerifierand metadata/table/view APIs so StackQL's successor-SDK paths cannot bypass the setting.Validation
pkg/omnisdksuite passes on Linux/WSL (Windows-only shell/fsync failures were not papered over).Tagged release and coordination
Release v0.1.7-alpha01 tags the single squashed feature commit f510d0c and pins signing v0.1.0-alpha01. Existing v0.1.6-alpha14 belongs to an independent gap-narrow feature branch, so this migration uses a distinct prerelease line without importing unrelated work. Public module resolution, tidy, document verification tests and the complete build pass.
MERGE METHOD: CREATE A MERGE COMMIT. Do not squash or rebase this PR: preserve the exact tagged commit in main history. After merging, verify git merge-base --is-ancestor v0.1.7-alpha01 origin/main succeeds. Never move a published tag; fixes require a new prerelease and downstream CI.
Order: provider-tests stackql/stackql-provider-tests#2 first; this PR and stackql/any-sdk#155 in parallel; then squash-merge stackql/stackql#869 and publish the binary; finally merge stackql/stackql-provider-registry#487 with a merge commit. Confirm the provider-test latest-binary download receives the new build before registry cutover. The approved raw-v1 protocol and opt-in defaults are unchanged.
Latest semver CI verification
Both PR checks passed at tagged commit f510d0c, including build/vet/race/coverage and mock-S3 Robot tests: https://github.com/stackql-labs/omnisdk/actions/runs/40050512793. All downstream core checks passed with named versions: https://github.com/stackql/stackql/actions/runs/40050605476. No PRs have been merged; use Create a merge commit to bring the release tag into main history.
Closes #17