Repository navigation
verify-ml-dsa-provider-documents - #155
Open
jeffreyaven wants to merge 1 commit into
Open
jeffreyaven wants to merge 1 commit into
jeffreyaven wants to merge 1 commit into
Conversation
This was referenced Oct 23, 2026
Use the shared raw-v1 ML-DSA-65 verifier for local, cached and remote documents. Preserve nopVerify and remove legacy certificate/sidecar verification. 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
e1ba4ac to
e35c9de
Compare
Member
Author
|
Coordinated cutover is ready and core #869 is approved. This library PR has all-green CI, but GitHub still requires a native approval here (there are no reviews yet). Requested your review so we can proceed without bypassing branch protection. Please approve this PR, then it must be merged using Create a merge commit to preserve tagged commit e35c9de / v0.6.1-beta02 in main. Core/release and registry cutover remain gated on this merge. |
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
.sigfetching; invalid embedded documents cannot fall back to legacy signatures.nopVerifyand existing default behavior. ExplicitpublicKeysreplaces the embedded roots for private registries.Validation
go vetalso reports two existing malformed YAML tags in registry metadata structs; these unrelated pre-existing tags are unchanged.Tagged release and coordination
Release v0.6.1-beta02 tags the single squashed feature commit e35c9de. It pins signing v0.1.0-alpha01 instead of a feature-commit pseudo-version. Public module resolution, tidy, focused registry/signature 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.6.1-beta02 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-labs/omnisdk#23 in parallel; then squash-merge stackql/stackql#869 and publish the new 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
All PR checks passed at tagged commit e35c9de, including Linux/Windows/macOS builds and tests: https://github.com/stackql/any-sdk/actions/runs/40050519071. All downstream core checks passed with the named versions: https://github.com/stackql/stackql/actions/runs/40050605476. Required maintainer approval remains. No PRs have been merged; use Create a merge commit to bring the release tag into main history.
Closes #153