Skip to content

Commit

Permalink
docs: remove beta warning from docker manifests feature
Browse files Browse the repository at this point in the history
Signed-off-by: Carlos A Becker <caarlos0@users.noreply.github.com>
  • Loading branch information
caarlos0 committed Jul 19, 2022
1 parent 3cf64c1 commit 7aeebb1
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 7 deletions.
2 changes: 1 addition & 1 deletion internal/pipe/docker/manifest.go
Expand Up @@ -15,7 +15,7 @@ import (
"github.com/goreleaser/goreleaser/pkg/context"
)

// ManifestPipe is beta implementation of for the docker manifest feature,
// ManifestPipe is an implementation for the docker manifest feature,
// allowing to publish multi-arch docker images.
type ManifestPipe struct{}

Expand Down
8 changes: 2 additions & 6 deletions www/docs/customization/docker_manifest.md
Expand Up @@ -10,10 +10,6 @@ Notice that if you have something in the `docker_manifests` section in your
config file, GoReleaser will add the manifest's to the release notes
instead of the Docker images names.

!!! warning
Please note that this is a beta feature, and it may change or be removed
at any time.

!!! warning
Notice that the images used in the manifest **need to be pushed** for this to work.
This is a limitation of how `docker manifest create` works.
Expand Down Expand Up @@ -81,11 +77,11 @@ docker_manifests:
We basically build and push our images as usual, but we also add a new
section to our config defining which images are part of which manifests.

GoReleaser will create and publish the manifest in its publish phase.
GoReleaser will create and publish the manifest in its publishing phase.

!!! warning
Unfortunately, the manifest tool needs the images to be pushed to create
the manifest, that's why we both create and push it in the publish phase.
the manifest, that's why we both create and push it in the publishing phase.

## Example config

Expand Down

0 comments on commit 7aeebb1

Please sign in to comment.