feat: add CRE workflow deploy changeset and operation

[ecPablo]

Adds 1 operation and 1 changeset to deploy a CRE workflow. These serve as examples for basic workflow deployment using the CRE CLI. Operation can be composed to create more complex changesets or sequences. The operation will:

• Resolve the binary location and put it in a local temp dir
• Resolve the configuration location
• Resolve the project.yaml location
• Build the context.yaml file with the provided workflow registries. (It's possible we can drop this when we have the new version of the CLI with api key support, for now we are leaving it as it does not affect the deployment process)
• Injects deployer key if the registry is on chain.
• Calls the CRE CLI via the CLIRunner provided by CLDF.

AI Summary

This pull request introduces a new CRE workflow deploy changeset and operation, enabling automated deployment of CRE workflows via the CLI. It includes robust input validation, integration with the deployment framework, and comprehensive unit tests for both the changeset and operation. The documentation is also updated to describe the new package and its structure.

CRE Workflow Deploy Feature

• Added CREWorkflowDeployChangeset in cre/changesets/workflow_deploy.go to resolve workflow artifacts, validate inputs, and trigger the CRE CLI workflow deploy operation. This includes precondition checks for environment and input validity.
• Implemented CREWorkflowDeployOp in cre/operations/workflow_deploy.go, which prepares workflow artifacts, builds required config files, and invokes the CRE CLI with appropriate arguments and environment. Handles result reporting and error propagation.

Testing

• Added unit tests for the changeset in cre/changesets/workflow_deploy_test.go, covering various precondition scenarios and input validation.
• Added unit tests for the operation in cre/operations/workflow_deploy_test.go, including CLI invocation, argument construction, error handling, and output propagation.

Documentation

• Updated README.md to document the new cre package, its purpose, main changeset, operation, and package structure.

[Copilot]

Pull request overview

Adds a new cre package providing an example changeset + operation for deploying a CRE workflow via the CRE CLI, including artifact resolution and operation execution through the deployments framework.

Changes:

• Introduces CREWorkflowDeployOp to assemble workflow artifacts/config files and invoke cre workflow deploy.
• Adds CREWorkflowDeployChangeset to validate inputs/environment and execute the operation.
• Updates module dependencies and README documentation for the new cre package.

Reviewed changes

Copilot reviewed 6 out of 8 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
README.md	Documents the new cre package, its main changeset/operation, and layout.
go.mod	Adds direct + indirect dependencies required for CRE deploy integration and tests.
go.sum	Adds checksums for newly introduced dependencies.
cre/operations/workflow_deploy.go	Implements the CRE workflow deploy operation, including context/workflow config generation and CLI invocation.
cre/operations/workflow_deploy_test.go	Adds unit tests for the operation and arg construction.
cre/changesets/workflow_deploy.go	Implements the changeset wrapper around the operation with precondition checks + env loading.
cre/changesets/workflow_deploy_test.go	Adds unit tests for changeset precondition validation.
.gitignore	Ignores .idea/ directory.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 6 out of 8 changed files in this pull request and generated 3 comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 6 out of 8 changed files in this pull request and generated 1 comment.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[gustavogama-cll]

I think you should add .golangci-lint (and maybe also .tool-versions) to this PR. And then run the linter locally, to address several issues it'll catch:

$ asdf exec golangci-lint run -v ./...
INFO golangci-lint has version 2.8.0 built with go1.25.5 from e2e40021 on 2026-01-07T21:29:47Z
INFO [config_reader] Config search paths: [./ /Users/gama/cll/cld-changesets /Users/gama/cll /Users/gama /Users /]
INFO [config_reader] Used config file .golangci.yml
INFO [config_reader] Module name "github.com/smartcontractkit/cld-changesets"
INFO maxprocs: Leaving GOMAXPROCS=14: CPU quota undefined
INFO [goenv] Read go env for 6.359041ms: map[string]string{"GOCACHE":"/Users/gama/Library/Caches/go-build", "GOROOT":"/opt/homebrew/Cellar/go/1.25.7/libexec"}
INFO [lintersdb] Active 45 linters: [asciicheck bidichk bodyclose containedctx copyloopvar decorder depguard dogsled dupword durationcheck errcheck errchkjson errname errorlint exhaustive fatcontext goconst goimports gosec govet ineffassign intrange loggercheck makezero mirror misspell nilerr nilnil nlreturn noctx paralleltest perfsprint prealloc reassign revive spancheck staticcheck testifylint thelper unconvert unparam unused usestdlibvars wastedassign whitespace]
INFO [loader] Go packages loading at mode 8767 (compiled_files|deps|exports_file|files|name|types_sizes|imports) took 752.654042ms
INFO [runner/filename_unadjuster] Pre-built 0 adjustments in 588.333µs
INFO [linters_context/goanalysis] analyzers took 1m44.46339616s with top 10 stages: buildir: 1m1.272321996s, exhaustive: 7.916269705s, fact_deprecated: 5.76459826s, printf: 5.719533311s, ctrlflow: 4.990957554s, nilness: 4.021660681s, fact_purity: 3.733141212s, typedness: 2.975869126s, inspect: 2.534547482s, SA5012: 2.438052544s
INFO [runner/exclusion_paths] Skipped 0 issues by pattern "third_party$"
INFO [runner/exclusion_paths] Skipped 0 issues by pattern "builtin$"
INFO [runner/exclusion_paths] Skipped 0 issues by pattern "examples$"
INFO [runner/exclusion_rules] Skipped 0 issues by rules: [Path: "(.+)_test\\.go", Linters: "goconst"]
INFO [runner/exclusion_rules] Skipped 0 issues by rules: [Text: "SA1019:.*aws-sdk-go.*is deprecated", Path: "(.+)\\.go", Linters: "staticcheck"]
INFO [runner/exclusion_rules] Skipped 0 issues by rules: [Path: "third_party$", Linters: "goimports"]
INFO [runner/exclusion_rules] Skipped 0 issues by rules: [Path: "builtin$", Linters: "goimports"]
INFO [runner/exclusion_rules] Skipped 0 issues by rules: [Path: "examples$", Linters: "goimports"]
INFO [runner/max_same_issues] 6/9 issues with text "return with no blank line before" were hidden, use --max-same-issues
INFO [runner/max_same_issues] 6/9 issues with text "test helper function should start from t.Helper()" were hidden, use --max-same-issues
INFO [runner/max_same_issues] 3/6 issues with text "error-format: fmt.Errorf can be replaced with errors.New" were hidden, use --max-same-issues
INFO [runner] Issues before processing: 38, after processing: 16
INFO [runner] Processors filtering stat (in/out): generated_file_filter: 38/38, diff: 31/31, max_from_linter: 16/16, fixer: 31/31, max_same_issues: 31/16, path_shortener: 16/16, severity-rules: 16/16, max_per_file_from_linter: 31/31, path_prettifier: 16/16, path_absoluter: 38/38, path_relativity: 38/38, exclusion_paths: 38/38, exclusion_rules: 38/31, nolint_filter: 31/31, uniq_by_line: 31/31, source_code: 16/16, sort_results: 16/16, cgo: 38/38, filename_unadjuster: 38/38, invalid_issue: 38/38
INFO [runner] processing took 1.211828ms with stages: nolint_filter: 663.332µs, generated_file_filter: 204.792µs, exclusion_rules: 136.542µs, source_code: 95.624µs, exclusion_paths: 52.291µs, max_same_issues: 23.208µs, path_relativity: 22.457µs, uniq_by_line: 3.542µs, sort_results: 2.708µs, invalid_issue: 1.416µs, max_from_linter: 1.333µs, cgo: 1.208µs, path_shortener: 958ns, max_per_file_from_linter: 625ns, path_absoluter: 376ns, filename_unadjuster: 375ns, path_prettifier: 334ns, fixer: 333ns, diff: 333ns, severity-rules: 41ns
INFO [runner] linters took 8.452736s with stages: goanalysis_metalinter: 8.451459625s
cre/operations/workflow_deploy.go:93:6: shadow: declaration of "err" shadows declaration at line 71 (govet)
		if err := os.MkdirAll(bundleDir, 0o700); err != nil {
		   ^
cre/operations/workflow_deploy.go:102:6: shadow: declaration of "err" shadows declaration at line 71 (govet)
		if err := copyFile(projectSrc, projectDest); err != nil {
		   ^
cre/changesets/workflow_deploy.go:37:2: return with no blank line before (nlreturn)
	return nil
	^
cre/changesets/workflow_deploy.go:61:2: return with no blank line before (nlreturn)
	return out, nil
	^
cre/changesets/workflow_deploy_test.go:29:2: return with no blank line before (nlreturn)
	return env
	^
cre/changesets/workflow_deploy_test.go:136:2: Function TestCREWorkflowDeployChangeset_Apply missing the call to method parallel in the test run (paralleltest)
	t.Run("success returns report", func(t *testing.T) {
	^
cre/changesets/workflow_deploy_test.go:167:2: Function TestCREWorkflowDeployChangeset_Apply missing the call to method parallel in the test run (paralleltest)
	t.Run("operation error returns report and error", func(t *testing.T) {
	^
cre/changesets/workflow_deploy_test.go:186:2: Function TestCREWorkflowDeployChangeset_Apply missing the call to method parallel in the test run (paralleltest)
	t.Run("on-chain registry injects deployer key env", func(t *testing.T) {
	^
cre/changesets/workflow_deploy.go:20:10: error-format: fmt.Errorf can be replaced with errors.New (perfsprint)
		return fmt.Errorf("CRERunner is not available in this environment")
		       ^
cre/changesets/workflow_deploy.go:23:10: error-format: fmt.Errorf can be replaced with errors.New (perfsprint)
		return fmt.Errorf("CRE CLI runner is not configured")
		       ^
cre/changesets/workflow_deploy.go:32:10: error-format: fmt.Errorf can be replaced with errors.New (perfsprint)
		return fmt.Errorf("deploymentRegistry is required")
		       ^
cre/changesets/workflow_deploy.go:25:18: QF1008: could remove embedded field "WorkflowBundle" from selector (staticcheck)
	if err := input.WorkflowBundle.Validate(); err != nil {
	                ^
cre/changesets/workflow_deploy_test.go:182:3: empty: use require.Empty (testifylint)
		require.Equal(t, "", output.Stdout)
		^
cre/operations/workflow_deploy_test.go:43:11: test helper function should start from t.Helper() (thelper)
			input: func(t *testing.T) CREWorkflowDeployInput {
			       ^
cre/operations/workflow_deploy_test.go:55:14: test helper function should start from t.Helper() (thelper)
			setupCLI: func(t *testing.T) *cremocks.MockCLIRunner {
			          ^
cre/operations/workflow_deploy_test.go:69:11: test helper function should start from t.Helper() (thelper)
			input: func(t *testing.T) CREWorkflowDeployInput {
			       ^
16 issues:
* govet: 2
* nlreturn: 3
* paralleltest: 3
* perfsprint: 3
* staticcheck: 1
* testifylint: 1
* thelper: 3
INFO File cache stats: 4 entries of total size 23.5KiB
INFO Memory: 94 samples, avg is 1523.1MB, max is 2699.0MB
INFO Execution took 9.213310042s

[Copilot]

Pull request overview

Copilot reviewed 8 out of 10 changed files in this pull request and generated no new comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 8 out of 10 changed files in this pull request and generated no new comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[ecPablo]

Thanks @gustavogama-cll, I've addressed most of the comments now

[graham-chainlink]

Not sure if it is worth extending the test engine to support testing with CRE
https://docs.cld.cldev.sh/guides/changesets/testing-changesets#run-a-single-changeset

Currently if users want to test a changeset that uses cre with test engine, it wont work, we might have to supply like a mock cre object. Something to think about too

[ecPablo]

Not sure if it is worth extending the test engine to support testing with CRE https://docs.cld.cldev.sh/guides/changesets/testing-changesets#run-a-single-changeset

Currently if users want to test a changeset that uses cre with test engine, it wont work, we might have to supply like a mock cre object. Something to think about too

Yeah it's a good point, it might be something we'll need to add. Although I'd prefer to add these utils for the graph ql go client so we are working on top of something more stable longterm.