Skip to content

Releases: redhat-actions/push-to-registry

Make input `username` and `password` optional

21 Apr 17:30
Compare
Choose a tag to compare
  • Make input username and password optional, so that user can skip these inputs if they are already logged in to container image registry.

Support to output single registry path

22 Feb 17:39
b5dbf66
Compare
Choose a tag to compare
  • Add output registy-path to output first element of registry-paths
  • Print image digest after every push to verify image digest for each tag
  • Print podman version at start of the action to verify that required version is being used
  • (Internal) Add Link checker workflow to identify dangling links

Modify error and info messages

25 Feb 19:37
Compare
Choose a tag to compare
  • Add output message if input tags is not provided
  • Modify output message if tag(s) are not found

v1.2: Solve issue when image is present in Podman and Docker both (#16)

19 Jan 15:36
23eb62f
Compare
Choose a tag to compare
* Solve issue when image is present in Podman and Docker both

If updated docker image is present in docker env then
docker image won't get used if image same name and tag
is already present in podman env.
To fix this, selected latest built image and removed the
image at the end from the podman env if image is pulled
from docker env.

Signed-off-by: divyansh42 <[email protected]>

v1.1: Solve issue when image is present in Podman and Docker both (#16)

19 Jan 15:36
23eb62f
Compare
Choose a tag to compare
* Solve issue when image is present in Podman and Docker both

If updated docker image is present in docker env then
docker image won't get used if image same name and tag
is already present in podman env.
To fix this, selected latest built image and removed the
image at the end from the podman env if image is pulled
from docker env.

Signed-off-by: divyansh42 <[email protected]>

v1: Solve issue when image is present in Podman and Docker both (#16)

08 Jan 15:55
23eb62f
Compare
Choose a tag to compare
* Solve issue when image is present in Podman and Docker both

If updated docker image is present in docker env then
docker image won't get used if image same name and tag
is already present in podman env.
To fix this, selected latest built image and removed the
image at the end from the podman env if image is pulled
from docker env.

Signed-off-by: divyansh42 <[email protected]>

v0.1

28 Nov 15:05
65d0a05
Compare
Choose a tag to compare
v0.1 Pre-release
Pre-release
Update action.yml