docs: add example release.yml that auto-publishes from CHANGELOG.md#714
Draft
samjewell wants to merge 1 commit into
Draft
docs: add example release.yml that auto-publishes from CHANGELOG.md#714samjewell wants to merge 1 commit into
samjewell wants to merge 1 commit into
Conversation
Companion to examples/extra/release-please.yml. Shows how to wire up build-plugin alongside an auto-publish step that restores the matching CHANGELOG.md section as the release body, preserves the attestation link, and marks the release as latest. Removes the per-release manual "edit draft body, mark latest" step for repos using release-please. Pattern developed in grafana/grafana-cube-datasource#323. Co-authored-by: Cursor <cursoragent@cursor.com>
grafana-plugins-platform-bot
Bot
moved this from 📬 Triage
to 🔬 In review
in Grafana Catalog Team
Contributor
|
@samjewell I believe uploading to Github Release is apart of the cd.yml flow. Here is an example in Logs Drilldown https://github.com/grafana/logs-drilldown/pull/1751/changes. The sad thing is that it's failing right now and I eventually had to turn it off because not all zip files were uploaded. Revert PR grafana/logs-drilldown#1785 The 🐛 ticket is here and I believe they are working on it #582 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Important
Draft, blocked on #713.
The auto-publish pattern works for any repo using release-please + build-plugin, regardless of whether the underlying `actions/plugins/release-please` action is generic or Grafana-internal-only. But shipping this example next to the existing `release-please.yml` example feels misleading until #713 is resolved one way or the other:
Either way, holding this until that decision is made.
Summary
Companion to `examples/extra/release-please.yml`. Shows how to wire up `build-plugin` alongside an auto-publish step that:
This removes the per-release manual "edit draft body, mark latest" step for repos using release-please.
Background
Pattern developed in grafana/grafana-cube-datasource#323 and used to release v0.6.0 of that plugin successfully. Without this step, every release needs a manual edit/publish step.
Test plan
Made with Cursor