Repository navigation
docs: describe the four agent tools as pinned, not always-latest - #120
Conversation
#116 pinned rtk, ralphex, the Claude Code CLI and agent-browser as Renovate-managed ARGs, but only the rebuild-cadence wording was corrected. The version-pinning claims were left behind, so several places still told readers these tools float at "latest". - ralphex-fe: replace the three "latest" rows with the pinned versions, and add an Automatic Rebuilds section — the image had no rebuild-trigger docs at all, which is why the stale rows never surfaced in a "daily" grep. Note that an agent-tool bump overwrites the bun-hugo tag instead of minting a new one, since the version tag derives from Bun and Hugo only. - claude-code: drop "Always-latest from GitHub Releases" and "pre-installed at latest"; correct AGENT_BROWSER_VERSION's default and document the three build args that #116 added but never listed. - root: document the Renovate path above the manual dispatch path, and say plainly what stays manual (base images, Bun/Hugo). Refs #119
Installing the app with "All repositories" defaults the repo to Silent mode (dryRun=lookup): Renovate scans and lists updates in the developer portal but creates no PRs and no issues — including the Dependency Dashboard and any config-warning issue. A correct config then looks indistinguishable from a broken one, which is exactly how this repo presented after #116 landed. Record the portal fix and the reason a config change can't substitute for it: mode is overridden by dryRun, which is admin-level. Refs #119
|
Added Root cause of "Renovate isn't doing anything" on this repo, now confirmed from the portal: Worth documenting because a correct config in Silent mode is indistinguishable from a broken one, and because |
Renovate's docs say to switch to "Interactive mode", but the Mend portal has no such control — it exposes a Silent mode toggle plus Automated PRs, Require config file, and Create onboarding PRs. Give the four toggle values so this is actionable from the UI as it exists. Refs #119
1 participant
What
Correct the version-pinning claims left behind by #116: the READMEs still described
rtk,ralphex, the Claude Code CLI, andagent-browseras floating at "latest".Why
#116 changed two facts — the rebuild cadence and the truth about versions — but only the cadence wording was fixed. Readers were told these tools track latest on every build, and
claude-code's Build Args table documented a default (AGENT_BROWSER_VERSION: latest) that no longer exists.The miss came from auditing only for
daily/cron.ralphex-fe/README.mdnever claimed a daily rebuild, so it never appeared in that grep — while its version table silently went stale.Changes
ralphex-fe/README.md: three "latest" rows → the pinned versions; new Automatic Rebuilds section (this image documented no rebuild trigger at all). Records a consequence worth knowing: because the version tag derives from Bun and Hugo only, an agent-tool bump refresheslatestand overwrites the existingbun{VERSION}-hugo{VERSION}tag rather than minting a new one.claude-code/README.md: drop "Always-latest from GitHub Releases" and "pre-installed in the image at latest"; fixAGENT_BROWSER_VERSION's default to0.32.3and add theRTK_VERSION/RALPHEX_VERSION/CLAUDE_CODE_VERSIONrows that Rebuild claude-code & ralphex-fe only on real tool updates (Renovate) #116 introduced but never documented.README.md: document the Renovate path above the manualworkflow_dispatchpath, and state what stays manual (base images, Bun/Hugo).ralphex-feto match the existing heading inclaude-code, so the cross-links share one anchor.Notes
ci.yml's path filters (**/Dockerfile,**/*.sh,.github/workflows/**,.hadolint.yaml) mean no checks will run here. Expected, not a stuck pipeline.master's Dockerfiles rather than transcribed, and both#automatic-rebuildsanchors were verified against their headings. The only surviving "latest" in these files is theclaude-code:latestimage tag, which is correct.master, which gives the Renovate app a webhook event to react to — useful, since it hasn't run yet.Closes #119