Commit 643d0e7
authored
fix: trigger Maven deploy on release-please published events (#1966)
## Summary
- Add `release: published` trigger to the deploy workflow so it fires
when release-please creates a GitHub Release (the existing `push: tags`
trigger doesn't fire because release-please uses `GITHUB_TOKEN` via the
API)
- Remove unused `.github/release.yml` (release notes config that was
never
applied — release-please supplies its own changelog)
## Test plan
- [x] Manually re-triggered v1.6.0 deploy by re-pushing the tag
- [ ] Next release-please release should automatically trigger the
deploy
Signed-off-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.com>1 parent c77112b commit 643d0e7
2 files changed
+3
-17
lines changedThis file was deleted.
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
5 | 5 | | |
6 | 6 | | |
7 | 7 | | |
| 8 | + | |
| 9 | + | |
| 10 | + | |
8 | 11 | | |
9 | 12 | | |
10 | 13 | | |
| |||
0 commit comments