Skip to content

Commit 2410094

Browse files
authored
Actions: Upload correct md5sums.txt path (#673)
1 parent 630563e commit 2410094

File tree

4 files changed

+15
-29
lines changed

4 files changed

+15
-29
lines changed

.github/workflows/build-plugin.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -147,7 +147,7 @@ jobs:
147147
with:
148148
files: |
149149
artifacts/*.zip
150-
md5sums.txt
150+
artifacts/md5sums.txt
151151
fail_on_unmatched_files: true
152152
make_latest: 'true'
153153
generate_release_notes: true

CHANGELOG.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
1-
## 4.0.1 (2025-07-22)
1+
## 4.0.1 & 4.0.2 (2025-07-22)
22

3-
This release only touches the build process of the plugin, as v4.0.0 did not release on the plugin catalog.
3+
This release only touches the build process of the plugin, as v4.0.0 and v4.0.1 did not release on the plugin catalog.
44
There is no difference from v4.0.0 for Docker users.
55

66
## 4.0.0 (2025-07-22)

docs/release_new_version.md

Lines changed: 11 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -1,41 +1,27 @@
11
# Release and publish a new version
22

3-
1. Every commit to master is a possible release.
4-
2. Version in plugin.json is used for deciding which version to release.
3+
Remember that every commit to master is a possible release.
54

65
## Prepare
76

87
1. Update `version` and `updated` properties in plugin.json.
98
2. Update CHANGELOG.md.
109
3. Merge/push changes to master.
11-
4. Commit is built in [Drone](https://drone.grafana.net/grafana/grafana-image-renderer).
1210

13-
## Promote release
11+
## Release
1412

15-
1. Open [Drone](https://drone.grafana.net/grafana/grafana-image-renderer) and find the build for your commit.
16-
2. Click on the `...` from the top-right corner to display the menu, then click on `Promote`.
17-
3. Fill the `Create deployment` form with the values below, and click on `Deploy`:
18-
- `Type` = `Promote`
19-
- `Target` = `release` *(write it manually)*
20-
- *(no parameters needed)*
21-
4. Once you've clicked on `Deploy` it will trigger a new pipeline with the release steps.
22-
23-
## Publish plugin to Grafana.com
24-
25-
Since the [migration to Drone](https://github.com/grafana/grafana-image-renderer/pull/394), this step that historically
26-
was needed to be performed manually is no longer required and is automatically performed by `publish_to_gcom` step.
27-
28-
**Note:** The step will time out, but the plugin update process will continue in the background.
13+
Tag a new version, either in the GitHub UI or pushing it from the CLI:
2914

3015
```
31-
<html>
32-
<head><title>504 Gateway Time-out</title></head>
33-
<body>
34-
<center><h1>504 Gateway Time-out</h1></center>
35-
<hr><center>nginx/1.17.9</center>
36-
</body>
37-
</html>
16+
$ git switch master
17+
$ git fetch
18+
$ git reset --hard origin/master
19+
$ git tag v0.0.0
20+
$ git push origin v0.0.0
3821
```
3922

23+
GitHub Actions takes care of _everything_ until you get to the Grafana Cloud deployment.
24+
4025
## Deploy into Grafana Cloud
26+
4127
Create a PR in [Deployment Tools](https://github.com/grafana/deployment_tools/blob/master/ksonnet/lib/render-service/images.libsonnet) with the new version.

plugin.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@
2424
"url": "https://github.com/grafana/grafana-image-renderer/blob/master/LICENSE"
2525
}
2626
],
27-
"version": "4.0.1",
27+
"version": "4.0.2",
2828
"updated": "2025-07-22"
2929
},
3030
"dependencies": {

0 commit comments

Comments
 (0)