Alexander Bayandin 2d6fd72177 GitHub Workflows: Fix crane for several registries (#4076) ...

Follow-up fix after https://github.com/neondatabase/neon/pull/4067

```
+ crane tag neondatabase/vm-compute-node-v14:3064 latest
Error: fetching "neondatabase/vm-compute-node-v14:3064": GET https://index.docker.io/v2/neondatabase/vm-compute-node-v14/manifests/3064: MANIFEST_UNKNOWN: manifest unknown; unknown tag=3064
```

I reverted back the previous approach for promoting images
(login to one registry, save images to local fs, logout and login to
another registry, and push images from local fs). It turns out what
works for one Google project (kaniko), doesn't work for another (crane)
[sigh]

2023-04-25 23:58:59 +01:00

..

benchmarking.yml

GitHub Workflows: use '!cancelled' instead of 'success or failure'

2023-04-12 15:22:18 +01:00

build_and_test.yml

GitHub Workflows: Fix crane for several registries (#4076)

2023-04-25 23:58:59 +01:00

deploy-dev.yml

Deploy proxies for preview enviroments (#4052)

2023-04-25 16:46:52 +02:00

deploy-prod.yml

Add storage broker deployment to us-east-1 (#4048)

2023-04-18 18:41:09 +03:00

neon_extra_builds.yml

GitHub Workflows: use ref_name instead of ref

2023-04-12 15:22:18 +01:00

pg_clients.yml

GitHub Workflows: use ref_name instead of ref

2023-04-12 15:22:18 +01:00

release.yml

Revert "Add neondatabase/release team as a default reviewers for storage"

2023-03-27 14:10:18 +04:00