rcourtman 7c9a572349 chore(ci): stop resurrecting the pulse-agent GHCR package ... The agent_runtime verify-only build pointed its registry buildcache at ghcr.io/<owner>/pulse-agent, a package no workflow publishes. A cache ref creates the package it points at, so every release recreated it and the repository's Packages sidebar advertised an empty pulse-agent entry that reads like a pullable agent image sitting beside the real pulse, pulse-control-plane and pulse-chart/pulse packages. The only release tag it ever carried is a stray v6.0.0-rc.3. Move the cache to ghcr.io/<owner>/pulse:agent-buildcache, alongside the runtime stage's existing pulse:buildcache tag, so it lives in the package that actually ships and shares backend-builder layers with the runtime build. TestAgentBuildCacheDoesNotResurrectPulseAgentPackage locks this in. It scans every workflow for registry-qualified refs to the pulse-agent package, collapsing ${{ }} expressions first so an interpolated owner cannot hide one behind its spaces, and asserts both the new cache target and the chart's published agent image default. Verified red on a restored buildcache ref and red again on a ref hidden behind ${{ github.repository_owner }}. Two stale claims corrected while here. The chart values comment said the old agent.image default was never published, when it did carry v6.0.0-rc.3. The deployment-installability contract called rcourtman/pulse the only image publish-docker.yml pushes, when the same workflow also pushes the MSP pulse-control-plane image. The contract now also forbids buildcache references to the pulse-agent package, which is what let this regress. Deleting the orphaned package itself remains a manual GHCR step.		2026-08-06 10:48:05 +01:00
..
helm/pulse	chore(ci): stop resurrecting the pulse-agent GHCR package	2026-08-06 10:48:05 +01:00
provider-msp	Self-issue the MSP evaluation licence, and fix two things it exposed	2026-08-03 18:14:05 +01:00