balena-io/Deploy to Balena
Automate release builds and deployments
View on GitHubTrust Signals
- Scorecard Score
- Scorecard 4–6scored Jul 6, 2026
- Maintenance Recency
- Activelast commit Jun 16, 2026
- License
- Apache 2.0
Pinned Snippet
uses: balena-io/deploy-to-balena-action@3653c472f0bb6a9885110328b28c3a80470b3b63 # v2.3.1tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| balena_token | Your balenaCloud API token | yes | — |
| fleet | Name of the fleet you want to build the release for | yes | — |
| github_token | Github access token | no | ${{ github.token }} |
| environment | Domain for the backend services to build your release | no | balena-cloud.com |
| versionbot | (Deprecated) Does the repository use VersionBot? | no | false |
| finalize | Should the action finalize a release after building | no | true |
| create_tag | Tag the git commit with the final balena release version | no | false |
| create_ref | Tag the git commit with the final balena release version | no | false |
| cache | If a release matching the commit already exists do not build | no | true |
| source | Specify custom path to Dockerfile/docker-compose for building release images | no | "" |
| dockerfile | Alternative Dockerfile name/path, relative to the source folder | no | "" |
| layer_cache | Use cached layers of previously built images for this project | no | true |
| registry_secrets | Image registry credentials (Balena secrets.json) | no | "" |
| default_branch | Branch for finalizing releases | no | "" |
| multi_dockerignore | Use service's dockerignore file | no | false |
| debug | Enable debug logs for balena push build | no | false |
| note | Enable adding a note to the release | no | "" |
Outputs
| name | description |
|---|---|
| release_id | ID of the release built |
| version | Version of the release built |