Alexander Bayandin b98419ee56 Fix allure report overwriting for different Postgres versions (#4806) ...

## Problem

We've got an example of Allure reports from 2 different runners for the
same build that started to upload at the exact second, making one
overwrite another

## Summary of changes
- Use the Postgres version to distinguish artifacts (along with the
build type)

2023-07-26 15:19:18 +01:00

..

allure-report-generate

Prevent unintentional Postgres submodule update (#4692)

2023-07-12 15:12:37 +01:00

allure-report-store

Run regressions tests on both Postgres 14 and 15 (#4192)

2023-05-12 15:28:51 +01:00

download

GitHub Workflows: print error messages to stderr

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

neon-branch-create

GitHub Workflows: print error messages to stderr

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

neon-branch-delete

GitHub Workflows: print error messages to stderr

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

neon-project-create

Nightly Benchmarks: Add free tier sized compute (#3969)

2023-04-06 19:18:24 +03:00

neon-project-delete

neon-project-create/delete: print project id to stdout (#3073)

2022-12-14 13:04:04 +00:00

run-python-test-set

Fix allure report overwriting for different Postgres versions (#4806)

2023-07-26 15:19:18 +01:00

save-coverage-data

github/workflows: upload artifacts to S3 (#2071)

2022-08-02 13:57:26 +01:00

upload

GitHub Workflows: print error messages to stderr

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