releaser-pleaser/.github/workflows
Julian Tölle 7d19a657e2 ci: use current code for releaser-pleaser action
The previous job always used the last release version of
releaser-pleaser. This caused two issues:

- if new flags were added to `action.yml` since the last release, the
  program errored because the flags are unknown.
- right after merging a release pr, the image reference was already
  updated, but no new container image was built yet.

This fixes both issues, by using a locally built version of
releaser-pleaser, which is always up-to-date and available.
2024-08-25 13:51:31 +02:00
..
ci.yaml chore: update golangci-lint 2024-08-20 17:37:46 +02:00
docs.yaml docs: setup mdbook (#27) 2024-08-24 16:23:42 +02:00
release.yaml fix(ci): ko pipeline permissions (#23) 2024-08-24 15:26:54 +02:00
releaser-pleaser.yaml ci: use current code for releaser-pleaser action 2024-08-25 13:51:31 +02:00