Send publish reports to Argus from the release job #7

New issue

Closed

opened 2026-10-30 06:31:48 +00:00 by Gilles · 0 comments

Gilles commented

2026-10-30 06:31:48 +00:00

Owner

Monitoring plan, phase 5 rollout (pilots: argus/backend#45, argus/frontend#35).

publish-release (ci-base) sends a publish report to Argus when ARGUS_UPLOAD_TOKEN is set: version, release page, artifacts with their size, dependencies. Wire it into both release steps (numbered release and devel snapshot).

New step "Collect publish details for Argus": /tmp/dependencies.txt = the direct requirements of go.mod (module version lines). A Go module has no artifact of its own, so the report carries the version, the release page and the dependencies. There is no devel snapshot here, so only the numbered release sends a report.

Monitoring plan, phase 5 rollout (pilots: argus/backend#45, argus/frontend#35). `publish-release` (ci-base) sends a `publish` report to Argus when `ARGUS_UPLOAD_TOKEN` is set: version, release page, artifacts with their size, dependencies. Wire it into both release steps (numbered release and devel snapshot). - New step "Collect publish details for Argus": `/tmp/dependencies.txt` = the direct requirements of `go.mod` (`module version` lines). A Go module has no artifact of its own, so the report carries the version, the release page and the dependencies. There is no devel snapshot here, so only the numbered release sends a report.

Gilles referenced this issue from a pull request that will close it,

2026-10-30 06:31:52 +00:00

Send publish reports to Argus from the release job #8

Gilles referenced this issue from a commit

2026-10-30 06:31:53 +00:00

ci: send publish reports to Argus from the release job

Gilles closed this issue

2026-10-30 08:13:23 +00:00

Gilles referenced this issue from a commit

2026-10-30 08:13:24 +00:00

Send publish reports to Argus from the release job (#8)