Repository navigation
Pick up the traust-sdk main merge: typed contracts, remediation surface, API clients - #60
Open
pshickeydev wants to merge 1 commit into
Open
pshickeydev wants to merge 1 commit into
pshickeydev wants to merge 1 commit into
Conversation
Code Review by Qodo🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)
Great, no issues found!Qodo reviewed your code and found no material issues that require reviewTip of the day💡 Did you know, you can open the rule or relationship behind a finding in one click |
pshickeydev
added a commit
to pshickeydev/traust-cli
that referenced
this pull request
Nov 12, 2026
…ce, API clients Bumps github.com/traust-security/traust-sdk/go from 8fd9fbd91252 to 0e2396cb981d, the development→main merge (traust-security#60): the typed traust package, the remediation surface, contracts regenerated at 83d90e75, and the new generated REST API clients for traust-core. No CLI-side API breakage: the CLI touches the SDK only through go/v1/skills and go/v1/ledger, both unchanged at the call sites. Verified: go build, full test suite green (throwaway test repos run with GIT_CONFIG_GLOBAL/SYSTEM=/dev/null so they don't inherit commit.gpgsign), live smoke runs of doctor, skills, runs, peek, result, and — mirroring the forward-scanning-pipeline consumer — a full Containerfile.toolkit-plus-feeds image build from this tree followed by an end-to-end TraustScanner run (deterministic opengrep/gitleaks/osv lane plus the claude agent lane on secure-code-audit with GLM 5.3 via EnMaaS): clean exit, result.json with the consumed fields, schema-valid report + markdown artifacts, session transcripts exported, findings parsed. The ledger wire path was not exercised (no ledger service available locally); ledger commands correctly fail-closed without TRAUST_LEDGER_URL. Assisted-by: GLM-5.3
pshickeydev
force-pushed
the
pick-up-sdk-main-merge
branch
from
November 12, 2026 05:40
c944780 to
5d16c9c
Compare
|
Code review by qodo was updated up to the latest commit 5d16c9c |
pshickeydev
added a commit
to pshickeydev/traust-cli
that referenced
this pull request
Nov 12, 2026
…ce, API clients Bumps github.com/traust-security/traust-sdk/go from 8fd9fbd91252 to 0e2396cb981d, the development→main merge (traust-security#60): the typed traust package, the remediation surface, contracts regenerated at 83d90e75, and the new generated REST API clients for traust-core. No CLI-side API breakage: the CLI touches the SDK only through go/v1/skills and go/v1/ledger, both unchanged at the call sites. Verified: go build, go vet, full test suite green with -race (throwaway test repos run with GIT_CONFIG_GLOBAL/SYSTEM=/dev/null so they don't inherit commit.gpgsign), live smoke runs of doctor, skills, runs, peek, result, and an end-to-end run from a full Containerfile.toolkit-plus- feeds image built from this tree: a secure-code-audit skill run through the claude harness (GLM 5.3) completed cleanly, with a result.json carrying the run/artifact/budget fields, schema-valid report + markdown artifacts, and session transcripts exported. The ledger wire path was not exercised (no ledger service available locally); ledger commands correctly fail-closed without TRAUST_LEDGER_URL. Assisted-by: GLM-5.3
pshickeydev
force-pushed
the
pick-up-sdk-main-merge
branch
from
November 12, 2026 06:52
5d16c9c to
b5c67a4
Compare
|
Code review by qodo was updated up to the latest commit b5c67a4 |
…ce, API clients Bumps github.com/traust-security/traust-sdk/go from 8fd9fbd91252 to 0e2396cb981d, the development→main merge (traust-security#60): the typed traust package, the remediation surface, contracts regenerated at 83d90e75, and the new generated REST API clients for traust-core. No CLI-side API breakage: the CLI touches the SDK only through go/v1/skills and go/v1/ledger, both unchanged at the call sites. Verified: go build, go vet, full test suite green with -race (throwaway test repos run with GIT_CONFIG_GLOBAL/SYSTEM=/dev/null so they don't inherit commit.gpgsign), live smoke runs of doctor, skills, runs, peek, result, and an end-to-end run from a full Containerfile.toolkit-plus- feeds image built from this tree: a secure-code-audit skill run through the claude harness (GLM 5.3) completed cleanly, with a result.json carrying the run/artifact/budget fields, schema-valid report + markdown artifacts, and session transcripts exported. The ledger wire path was not exercised (no ledger service available locally); ledger commands correctly fail-closed without TRAUST_LEDGER_URL. Assisted-by: GLM-5.3
pshickeydev
force-pushed
the
pick-up-sdk-main-merge
branch
from
November 12, 2026 22:08
b5c67a4 to
d6f0543
Compare
|
Code review by qodo was updated up to the latest commit d6f0543 |
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.
What
Bumps
github.com/traust-security/traust-sdk/gofrom8fd9fbd91252to0e2396cb981d— the development→main merge (traust-sdk#60): the typed traust package, the remediation surface, contracts regenerated at83d90e75, and the new generated REST API clients for traust-core.Diff is exactly
go.mod/go.sum(3 lines).Why
The ecosystem's development branches were merged to main; this picks up the result so the CLI builds against the current SDK.
Impact
None at the call sites: the CLI consumes the SDK only through
go/v1/skills(runner/provider) andgo/v1/ledger(views/ledger), both unchanged.Verification
go build ./...clean;go vetand the full test suite green with-race(throwaway test repos run withGIT_CONFIG_GLOBAL=/dev/null GIT_CONFIG_SYSTEM=/dev/nullso they don't inheritcommit.gpgsign)doctor,skills,runs,peek,resultContainerfile.toolkit-plus-feedsimage from this tree and ran an end-to-endsecure-code-auditskill run in it through the claude harness (GLM 5.3) — clean exit,result.jsonwith the run/artifact/budget fields, schema-valid report + markdown artifacts, session transcripts exportedledgercommands correctly fail closed withoutTRAUST_LEDGER_URL🤖 This pull request body is AI-generated.