Nikita Kalyanov 82174e359a don't push latest tags on release branch ...

before this change we pushed latest tag both on main
and on release. This could lead to akward situations when you
start using some freshly merged to main feature and then the
release happens and you start getting older image. It's possible
to bump into this both locally and in cloud CI.
The proposal is to only push latest on main. This is unlikely to
cause issues because now if someone merges after the release
latest is agin at main. However, the tag is more consistent
and not depend on timing of merges

2023-05-24 18:55:47 +03:00

..

benchmarking.yml

Nightly Benchmarks: add neonvm to pgbench-compare (#4225)

2023-05-16 12:46:28 +01:00

build_and_test.yml

don't push latest tags on release branch

2023-05-24 18:55:47 +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