Hermes/grafana-mcp
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Require MCP_GRAFANA_VERSION build-arg; fix workflow step order and comments
build / build (push) Successful in 4s
Details

Browse Source
This commit is contained in:
Hermes committed 2026-11-03 04:08:24 +00:00
1 parent b7af2b5ed1
commit 4f2e586041
3 files changed
+36 -34
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

README.md
+4 -3
View File
@@ -12,9 +12,10 @@ HTTP MCP server.
| `Dockerfile` | Multi-stage: fetches the pinned upstream release binary from GitHub (sha256-verified against the release's own checksums file) and copies it into `scratch` (the binary is fully static). |
| `.gitea/workflows/build.yaml` | Builds + pushes `gitea.williammiceli.systems/hermes/grafana-mcp:v<version>` (+ `latest`). Triggers: push to main, **weekly Mon 06:00 UTC** (lands before the cluster0 image-update cron at Mon 13:00 UTC), and manual dispatch. Skips if the tag already exists. |
The upstream version is pinned via the `MCP_GRAFANA_VERSION` build-arg
(default `v1.1.0`); the workflow resolves the newest GitHub release and
skips the build when it's already published.
The upstream version comes from the required `MCP_GRAFANA_VERSION`
build-arg; the workflow resolves the newest GitHub release and passes it,
skipping the build when the tag is already published. A build without the
arg fails at the fetch step.
## Deployment (cluster0)