Alexander Bayandin bf9fc77061 CI(pg-clients): unify workflow with build-and-test (#8160) ...

## Problem

`pg-clients` workflow looks different from the main `build-and-test`
workflow for historical reasons (it was my very first task at Neon, and 
back then I wasn't really familiar with the rest of the CI pipelines).
This PR unifies `pg-clients` workflow with `build-and-test`

## Summary of changes
- Rename `pg_clients.yml` to `pg-clients.yml`
- Run the workflow on changes in relevant files
- Create Allure report for tests
- Send slack notifications to `#on-call-qa-staging-stream` channel
(instead of `#on-call-staging-stream`)
- Update Client libraries once we're here

2024-07-04 14:58:01 +01:00

..

Sources/PostgresClientKitExample

Update client libs for test_runner/pg_clients to their latest versions (#4092)

2023-05-04 18:22:04 +01:00

.dockerignore

Add tests for different Postgres client libraries (#2008)

2022-07-05 12:22:58 +01:00

.gitignore

Add tests for different Postgres client libraries (#2008)

2022-07-05 12:22:58 +01:00

Dockerfile

CI(pg-clients): unify workflow with build-and-test (#8160)

2024-07-04 14:58:01 +01:00

Package.resolved

CI(pg-clients): unify workflow with build-and-test (#8160)

2024-07-04 14:58:01 +01:00

Package.swift

CI(pg-clients): unify workflow with build-and-test (#8160)

2024-07-04 14:58:01 +01:00