CI Release

Node catalog Actions

On this page

Semver release (release-it) in the workspace

Usage and specifics

Run the release command in the workspace. The default uses release-it; the repository and Git permissions must support the requested release.

Technical type : ci_release. Runtime : docker.

Credentials and prerequisites

This node defines no dedicated external credential. Remote sources or execution targets may still need their own access credentials.

See the credentials guide if a remote source or execution target requires access.

Parameters

Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.

Parameter	Type	Default	Values / limits
`command`	`string`	`"npx --yes release-it --ci"`	-; min 1
`workingDir`	`string`	-	-
`image`	`string`	-	-
`secretCredentialIds`	`array`	`[]`	-
`secretFiles`	`array`	`[]`	-; max 20
`secretFiles[].path`	`string`	-	-; min 1, max 1024
`secretFiles[].content`	`string`	-	-; max 1048576
`workspaceSource`	`union`	`{"kind":"upstream"}`	-
`workspaceSource.kind`	`literal`	`"upstream"`	`upstream`, `node`
`workspaceSource.key`	`string`	-	-; min 1
`executionTarget`	`union`	`{"kind":"host"}`	-
`executionTarget.kind`	`literal`	`"host"`	`host`, `remote_server`, `kube`, `swarm`
`executionTarget.serverId`	`string`	-	-; min 1
`executionTarget.provider`	`enum`	-	`aws`, `gcp`, `scaleway`, `ovh`, `azure`, `digitalocean`, `hetzner`
`executionTarget.clusterId`	`string`	-	-; min 1
`executionTarget.namespace`	`string`	-	-

Configuration help

command Release command: Publishing command (default: npx --yes release-it --ci). Prepare Git, push access and required secrets; Checkout credentials are only used for cloning.
workingDir Working directory (relative): Workspace subdirectory where commands run (e.g. apps/backend).
image Container image (shell): Image containing the tools your commands need. Defaults: oven/bun:1 for Shell and Verify; node:22-bookworm for Release.
secretCredentialIds Secrets: Secrets connections injected as environment variables of the script (process.env, os.environ...). The file carrying them is deleted as soon as the container starts.

Initial configuration

Initial catalog configuration example, to adapt before running. Keep secrets in credentials.

json

{
  "command": "npx --yes release-it --ci",
  "workspaceSource": {
    "kind": "upstream"
  },
  "executionTarget": {
    "kind": "host"
  }
}

Verification

Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.