mirror of
https://github.com/neondatabase/neon.git
synced 2025-12-22 21:59:59 +00:00
10cf5e7a38
## Problem There are two (related) problems with the previous handling of `cargo-deny`: - When a new advisory is added to rustsec that affects a dependency, unrelated pull requests will fail. - New advisories rely on pushes or PRs to be surfaced. Problems that already exist on main will only be found if we try to merge new things into main. ## Summary of changes We split out `cargo-deny` into a separate workflow that runs on all PRs that touch `Cargo.lock`, and on a schedule on `main`, `release`, `release-compute` and `release-proxy` to find new advisories.
31 lines
782 B
YAML
31 lines
782 B
YAML
self-hosted-runner:
|
|
labels:
|
|
- arm64
|
|
- large
|
|
- large-arm64
|
|
- small
|
|
- small-metal
|
|
- small-arm64
|
|
- us-east-2
|
|
config-variables:
|
|
- AZURE_DEV_CLIENT_ID
|
|
- AZURE_DEV_REGISTRY_NAME
|
|
- AZURE_DEV_SUBSCRIPTION_ID
|
|
- AZURE_PROD_CLIENT_ID
|
|
- AZURE_PROD_REGISTRY_NAME
|
|
- AZURE_PROD_SUBSCRIPTION_ID
|
|
- AZURE_TENANT_ID
|
|
- BENCHMARK_PROJECT_ID_PUB
|
|
- BENCHMARK_PROJECT_ID_SUB
|
|
- REMOTE_STORAGE_AZURE_CONTAINER
|
|
- REMOTE_STORAGE_AZURE_REGION
|
|
- SLACK_UPCOMING_RELEASE_CHANNEL_ID
|
|
- DEV_AWS_OIDC_ROLE_ARN
|
|
- BENCHMARK_INGEST_TARGET_PROJECTID
|
|
- PGREGRESS_PG16_PROJECT_ID
|
|
- PGREGRESS_PG17_PROJECT_ID
|
|
- SLACK_ON_CALL_QA_STAGING_STREAM
|
|
- DEV_AWS_OIDC_ROLE_MANAGE_BENCHMARK_EC2_VMS_ARN
|
|
- SLACK_ON_CALL_STORAGE_STAGING_STREAM
|
|
- SLACK_CICD_CHANNEL_ID
|