releaser-pleaser/.github/workflows
Julian Tölle 2d3a960939
feat: run one job concurrently to reduce chance of conflicts (#198)
Each run of releaser-pleaser acts on the same global state in the
forge. Therefore, parallel runs are unnecessary.

This commit also communicates to the GitHub and GitLab CI pipelines that
the releaser-pleaser jobs can be cancelled as early as possible.

- On GitHub Actions this can be guaranteed through the workflow
  settings. These settings are copied into each repository that uses
  releaser-pleaser, so users need to update this manually. I will add a
  note to the release notes for this.
- On GitLab CI/CD this requires the user to configure a project level setting to
  "auto-cancel redundant pipelines". We will not recommend user to set
  this, as it is quite invasive and can break their regular CI pipelines.
2025-06-14 13:43:35 +00:00
..
ci.yaml deps: update codecov/codecov-action digest to 18283e0 (#113) 2025-06-07 18:39:31 +02:00
docs.yaml deps: update dependency rust-lang/mdbook to v0.4.51 (#177) 2025-05-26 23:34:42 +00:00
mirror.yaml deps: update actions/checkout digest to 11bd719 (#89) 2024-11-15 14:52:43 +01:00
release.yaml deps: update actions/setup-go digest to d35c59a (#122) 2025-06-07 18:24:24 +02:00
releaser-pleaser.yaml feat: run one job concurrently to reduce chance of conflicts (#198) 2025-06-14 13:43:35 +00:00