For usage in critical environments with tight SLA
This is the most stable channel and recommended for usage in critical environments with tight SLA. We guarantee backward compatibility between Rock-Solid releases within minor branch (1.1.x). We guarantee that Stable release should become a Rock-Solid release not earlier than 2 weeks after broad testing.
{% raw %}
To install werf we strongly recommend following these instructions.
Alternatively, you can download werf binaries from here:
These binaries were signed with PGP and could be verified with the werf PGP public key. For example, werf binary can be downloaded and verified with gpg on Linux with these commands:
curl -sSLO "https://tuf.werf.io/targets/releases/2.22.0/linux-amd64/bin/werf" -O "https://tuf.werf.io/targets/signatures/2.22.0/linux-amd64/bin/werf.sig"
curl -sSL https://werf.io/werf.asc | gpg --import
gpg --verify werf.sig werf
{% endraw %}
Stable channel releases are mostly safe to use and we encourage to use this channel everywhere. We guarantee backward compatibility between Stable releases within minor branch (1.1.x). We guarantee that Early-Access release should become Stable not earlier than 2 weeks after internal testing.
{% raw %}
To install werf we strongly recommend following these instructions.
Alternatively, you can download werf binaries from here:
These binaries were signed with PGP and could be verified with the werf PGP public key. For example, werf binary can be downloaded and verified with gpg on Linux with these commands:
curl -sSLO "https://tuf.werf.io/targets/releases/2.27.1/linux-amd64/bin/werf" -O "https://tuf.werf.io/targets/signatures/2.27.1/linux-amd64/bin/werf.sig"
curl -sSL https://werf.io/werf.asc | gpg --import
gpg --verify werf.sig werf
{% endraw %}
For use in non critical environments or local development
These releases are mostly safe to use and can even be used in non critical environments or for local development. We do not guarantee backward compatibility between Early-Access releases.
{% raw %}
To install werf we strongly recommend following these instructions.
Alternatively, you can download werf binaries from here:
These binaries were signed with PGP and could be verified with the werf PGP public key. For example, werf binary can be downloaded and verified with gpg on Linux with these commands:
curl -sSLO "https://tuf.werf.io/targets/releases/2.27.1/linux-amd64/bin/werf" -O "https://tuf.werf.io/targets/signatures/2.27.1/linux-amd64/bin/werf.sig"
curl -sSL https://werf.io/werf.asc | gpg --import
gpg --verify werf.sig werf
{% endraw %}
For more broad testing of new features
These releases are for more broad testing of new features to catch regressions. We do not guarantee backward compatibility between Beta releases.
{% raw %}
To install werf we strongly recommend following these instructions.
Alternatively, you can download werf binaries from here:
These binaries were signed with PGP and could be verified with the werf PGP public key. For example, werf binary can be downloaded and verified with gpg on Linux with these commands:
curl -sSLO "https://tuf.werf.io/targets/releases/2.27.1/linux-amd64/bin/werf" -O "https://tuf.werf.io/targets/signatures/2.27.1/linux-amd64/bin/werf.sig"
curl -sSL https://werf.io/werf.asc | gpg --import
gpg --verify werf.sig werf
{% endraw %}
These releases can bring new features, but are unstable. We do not guarantee backward compatibility between Alpha releases.
{% raw %}
To install werf we strongly recommend following these instructions.
Alternatively, you can download werf binaries from here:
These binaries were signed with PGP and could be verified with the werf PGP public key. For example, werf binary can be downloaded and verified with gpg on Linux with these commands:
curl -sSLO "https://tuf.werf.io/targets/releases/2.27.1/linux-amd64/bin/werf" -O "https://tuf.werf.io/targets/signatures/2.27.1/linux-amd64/bin/werf.sig"
curl -sSL https://werf.io/werf.asc | gpg --import
gpg --verify werf.sig werf
{% endraw %}
For usage in critical environments with tight SLA
This is the most stable channel and recommended for usage in critical environments with tight SLA. We guarantee backward compatibility between Rock-Solid releases within minor branch (1.1.x). We guarantee that Stable release should become a Rock-Solid release not earlier than 2 weeks after broad testing.
{% raw %}# Features
[compose] docker-compose run command support
[compose] Support for positional arguments to build and forward
specific images
If one or more IMAGE_NAME parameters specified, werf will build and
forward only these images
werf compose up [IMAGE_NAME...] [options] [--docker-compose-options="OPTIONS"] [--docker-compose-command-options="OPTIONS"] [--] [SERVICE...]
[compose] Fix certain service names specified by the user are ignored
[container registry] Fix processing of reference with digest
The user may have encountered related issues when using the base image
(from) with digest (REPO@DIGEST, REPO:TAG@DIGEST).
WARNING: cannot get base image id (alpine@sha256:69e70a79f2d41ab5d637de98c1e0b055206ba40a8145e7bddb55ccc04e13cf8f): can not get base image id from registry (alpine@sha256:69e70a79f2d41ab5d637de98c1e0b055206ba40a8145e7bddb55ccc04e13cf8f): repository can only contain the runes `abcdefghijklmnopqrstuvwxyz0123456789_-./`: alpine@sha256
WARNING: using existing image alpine@sha256:69e70a79f2d41ab5d637de98c1e0b055206ba40a8145e7bddb55ccc04e13cf8f without pull
[git_repo] Move common methods from git_repo local/remote to base
[conveyor] Refactoring of werf config images processing
Improvements related to tests, coverage, and GitHub Actions workflows
{% endraw %}
Stable channel releases are mostly safe to use and we encourage to use this channel everywhere. We guarantee backward compatibility between Stable releases within minor branch (1.1.x). We guarantee that Early-Access release should become Stable not earlier than 2 weeks after internal testing.
{% raw %}# Features
[compose] docker-compose run command support
[compose] Support for positional arguments to build and forward
specific images
If one or more IMAGE_NAME parameters specified, werf will build and
forward only these images
werf compose up [IMAGE_NAME...] [options] [--docker-compose-options="OPTIONS"] [--docker-compose-command-options="OPTIONS"] [--] [SERVICE...]
[compose] Fix certain service names specified by the user are ignored
[container registry] Fix processing of reference with digest
The user may have encountered related issues when using the base image
(from) with digest (REPO@DIGEST, REPO:TAG@DIGEST).
WARNING: cannot get base image id (alpine@sha256:69e70a79f2d41ab5d637de98c1e0b055206ba40a8145e7bddb55ccc04e13cf8f): can not get base image id from registry (alpine@sha256:69e70a79f2d41ab5d637de98c1e0b055206ba40a8145e7bddb55ccc04e13cf8f): repository can only contain the runes `abcdefghijklmnopqrstuvwxyz0123456789_-./`: alpine@sha256
WARNING: using existing image alpine@sha256:69e70a79f2d41ab5d637de98c1e0b055206ba40a8145e7bddb55ccc04e13cf8f without pull
[git_repo] Move common methods from git_repo local/remote to base
[conveyor] Refactoring of werf config images processing
Improvements related to tests, coverage, and GitHub Actions workflows
{% endraw %}
For use in non critical environments or local development
These releases are mostly safe to use and can even be used in non critical environments or for local development. We do not guarantee backward compatibility between Early-Access releases.
{% raw %}# Features
[compose] docker-compose run command support
[compose] Support for positional arguments to build and forward
specific images
If one or more IMAGE_NAME parameters specified, werf will build and
forward only these images
werf compose up [IMAGE_NAME...] [options] [--docker-compose-options="OPTIONS"] [--docker-compose-command-options="OPTIONS"] [--] [SERVICE...]
[compose] Fix certain service names specified by the user are ignored
[container registry] Fix processing of reference with digest
The user may have encountered related issues when using the base image
(from) with digest (REPO@DIGEST, REPO:TAG@DIGEST).
WARNING: cannot get base image id (alpine@sha256:69e70a79f2d41ab5d637de98c1e0b055206ba40a8145e7bddb55ccc04e13cf8f): can not get base image id from registry (alpine@sha256:69e70a79f2d41ab5d637de98c1e0b055206ba40a8145e7bddb55ccc04e13cf8f): repository can only contain the runes `abcdefghijklmnopqrstuvwxyz0123456789_-./`: alpine@sha256
WARNING: using existing image alpine@sha256:69e70a79f2d41ab5d637de98c1e0b055206ba40a8145e7bddb55ccc04e13cf8f without pull
[git_repo] Move common methods from git_repo local/remote to base
[conveyor] Refactoring of werf config images processing
Improvements related to tests, coverage, and GitHub Actions workflows
{% endraw %}
For more broad testing of new features
These releases are for more broad testing of new features to catch regressions. We do not guarantee backward compatibility between Beta releases.
{% raw %}# Fixes
Fix werf-render command error shadowing and logging
werf render (--verbose|--debug) should enable verbose or debug mode, but it was not happened.{% endraw %}
These releases can bring new features, but are unstable. We do not guarantee backward compatibility between Alpha releases.
{% raw %}# Docs
[publication] Add recent publications
[docs] Advanced/Supported container registries: add Yandex Container Registry
Fix werf does not load secret values files outside of helm chart dir
{% endraw %}