Repository navigation
build(release): prepare offline auditor v0.1.1 - #115
Merged
Merged
Conversation
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.
Prepare offline auditor v0.1.1
Closes #6
PR type
Summary
Changes
cmd/ci-trust/release_test.gocmd/ci-trust/release_export_test.godocs/releases/0.1.1.mdREADME.mdTHIRD_PARTY_NOTICES.mdTest plan
ci-trust "0.1.1"/ exit 0 / empty stderr.go test -count=1 ./...andgo vet ./...passed offline after a separately authorized private Windows temp-environment correction. The initial local suite failure remains recorded, not rewritten as success; no product workaround was added.Contributor checklist
type:*label:type:choreat creation.Co-Authored-Bytrailers.Risk: item 5 (native release metadata/delivery). Writer and independent source checks are complete; native assessment was unassessable with RDD off, not approval. Preserve normal merge history and branches; no new workflow, dependencies, runtime admission or execution-efficacy claim.