JC Grünhage 10cf5e7a38 Move cargo-deny into a separate workflow on a schedule (#10289) ...

## 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.

2025-01-31 13:42:59 +00:00

..

actions

Test ingest_benchmark with different stripe size and also PostgreSQL version 17 (#10510)

2025-01-27 21:06:05 +00:00

ISSUE_TEMPLATE

[infra/notes] impr: add issue types to issue templates (#10018)

2025-01-31 06:29:06 +00:00

PULL_REQUEST_TEMPLATE

Migrate links from wiki to notion (#5862)

2023-11-14 15:36:47 +00:00

workflows

Move cargo-deny into a separate workflow on a schedule (#10289)

2025-01-31 13:42:59 +00:00

actionlint.yml

Move cargo-deny into a separate workflow on a schedule (#10289)

2025-01-31 13:42:59 +00:00

file-filters.yaml

Move cargo-deny into a separate workflow on a schedule (#10289)

2025-01-31 13:42:59 +00:00

pull_request_template.md

Remove checklist from the PR template (#9702)

2024-11-11 17:01:02 +00:00