Skip to content

chore: verify GAF CLI-1826 TOON UFM presenter - #7226

Draft
robertolopezlopez wants to merge 1 commit into
mainfrom
chore/verify-gaf-739-cli-1826
Draft

chore: verify GAF CLI-1826 TOON UFM presenter#7226
robertolopezlopez wants to merge 1 commit into
mainfrom
chore/verify-gaf-739-cli-1826

Conversation

@robertolopezlopez

@robertolopezlopez robertolopezlopez commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

Pull Request Submission Checklist

  • Follows CONTRIBUTING guidelines
  • Commit messages are release-note ready
  • Includes detailed description of changes
  • Contains risk assessment
  • No breaking API changes
  • GAF functionality is covered by snyk/go-application-framework#739
  • Includes manual validation
  • GitBook documentation is not required for this dependency-only change
  • No product update for CLI users yet

What does this PR do?

Verifies GAF PR #739 (CLI-1826) by bumping github.com/snyk/go-application-framework from v0.20.0 to pre-release v0.21.1-0.20260904162906-1889c7c76491 (1889c7c) in cliv2 and cliv2-private.

This GAF change adds SCA and Secrets UFM TOON presentation (byte-matched to CLI-1824 goldens) and wires TOON_MIME_TYPE into HandleContentTypeUnifiedModel. This CLI PR is dependency-only; user-facing --toon flags are still not registered in the CLI.

Where should the reviewer start?

Review cliv2/go.mod and cliv2-private/go.mod; remaining changes are generated go.sum updates.

How should this be manually tested?

Validated locally against GAF feat/CLI-1826 @ 1889c7c764911fcdb0fddd81073ca976314e11d5:

cd cliv2 && go get github.com/snyk/go-application-framework@1889c7c764911fcdb0fddd81073ca976314e11d5
cd cliv2 && go mod tidy
cd cliv2-private && go get github.com/snyk/go-application-framework@1889c7c764911fcdb0fddd81073ca976314e11d5
cd cliv2-private && go mod tidy
cd cliv2 && make test          # exit 0
cd cliv2 && go test ./pkg/core # exit 0
make build                     # exit 0
./binary-releases/snyk-macos-arm64 --version
./binary-releases/snyk-macos-arm64 whoami

GAF TOON presenter/output-workflow tests (run from local GAF checkout at same commit):

go test ./internal/presenters/... -count=1 -run 'Ufm|TOON|Toon|toon' -v
go test ./pkg/local_workflows/output_workflow/... -count=1 -run 'Toon|toon|TOON'

Evidence

Check Command Result
CLI Go tests cd cliv2 && make test exit 0; all packages ok
CLI core tests cd cliv2 && go test ./pkg/core exit 0 (10.966s)
CLI build make build exit 0; installed binary-releases/snyk-macos-arm64
CLI smoke ./binary-releases/snyk-macos-arm64 --version / whoami version prints; auth works
GAF TOON goldens go test ./internal/presenters/... -run 'Ufm|TOON|Toon|toon' -v TestRenderTemplate_TOON_goldens SCA/Secrets representative + empty: PASS
GAF output workflow go test ./pkg/local_workflows/output_workflow/... -run 'Toon|toon|TOON' exit 0

Note: snyk test --help and snyk secrets test --help do not yet expose --toon; end-user TOON output requires a follow-up CLI change to register output-workflow flags. This PR confirms the bumped GAF integrates cleanly with the CLI build and test suite.

What's the product update that needs to be communicated to CLI users?

None from this dependency bump alone.

Risk assessment (Low | Medium | High)?

Low. Dependency-only bump to a GAF pre-release commit; no CLI source changes.

What are the relevant tickets?

Made with Cursor

@snyk-io

snyk-io Bot commented Sep 4, 2026

Copy link
Copy Markdown

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues
Code Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

Bump go-application-framework to PR #739 commit 1889c7c so the CLI
consumes SCA and Secrets UFM TOON presentation ahead of GAF merge.

Co-authored-by: Cursor <cursoragent@cursor.com>
@robertolopezlopez
robertolopezlopez force-pushed the chore/verify-gaf-739-cli-1826 branch from 33704fa to db6d937 Compare September 7, 2026 07:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant