Repository navigation
build(deps): bump headroom-ai from 0.37.0 to 0.42.0 in /python - #165
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [headroom-ai](https://github.com/headroomlabs-ai/headroom) from 0.37.0 to 0.42.0. - [Release notes](https://github.com/headroomlabs-ai/headroom/releases) - [Changelog](https://github.com/headroomlabs-ai/headroom/blob/main/CHANGELOG.md) - [Commits](headroomlabs-ai/headroom@v0.37.0...v0.42.0) --- updated-dependencies: - dependency-name: headroom-ai dependency-version: 0.42.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
Dependabot bump of headroom-ai 0.37.0 → 0.42.0 in python/requirements-headroom.txt, a Dependabot-tracking anchor file that's never actually installed from.
Should fix: action.yml's headroom_version input default was not updated to match — it's still "0.37.0" — contrary to the explicit instruction in this very file's own header comment. Since action.yml's default is what's actually installed at runtime, merging as-is leaves the real pin at 0.37.0 while Dependabot believes the bump is done (and won't reopen a PR for 0.42.0). This dependency isn't covered by dependabot.yml's automated investigate job (that only runs for the anthropics/claude-code-action upstream pin), so there's no automation keeping the two in sync here — see the inline comment.
Title and description are Dependabot's own standard, specific form and already complete, so I left them as-is. No other changes in this diff.
| # the two in sync by hand (see README.md's "Context compression (Headroom)" section): when this file's | ||
| # version bumps, update action.yml's default to match in the same PR. | ||
| headroom-ai[proxy]==0.37.0 | ||
| headroom-ai[proxy]==0.42.0 |
There was a problem hiding this comment.
🟠 Should fix [policy]: this file's own header comment (lines 1-5) says to "update action.yml's default to match in the same PR" whenever this pin bumps, but action.yml's headroom_version input still defaults to "0.37.0" (action.yml:378). This file is a Dependabot-tracking anchor only — it is "never installed from directly by action.yml" (per its own comment) — so action.yml's default is what actually gets installed at runtime (action.yml:1322). Merging as-is leaves the action still installing 0.37.0 while this anchor now says 0.42.0, which also means Dependabot will consider the 0.42.0 bump already applied and won't reopen a PR for it, permanently stalling the real pin at 0.37.0 until someone notices by hand.
This is a non-upstream (headroom-ai, not anthropics/claude-code-action) dependency bump, so .github/workflows/dependabot.yml's investigate job — which only runs for is-upstream == true — never touches this; nothing in the automated pipeline keeps the two in sync for this dependency, so this review is the actual backstop the file's comment relies on.
If you'd like me to fix this, comment:
@claude bump action.yml's headroom_version input default from "0.37.0" to "0.42.0" to match python/requirements-headroom.txt
|
🗜️ Headroom context compression
|
Bumps headroom-ai from 0.37.0 to 0.42.0.
Release notes
Sourced from headroom-ai's releases.
... (truncated)
Changelog
Sourced from headroom-ai's changelog.
... (truncated)
Commits
17d38e5chore: release 0.42.0 (#4228)a904210feat(proxy): report the same tool savings on gateway /v1/compress as the prox...3fef15dfix(offline): keep litellm's pricing table local under HEADROOM_OFFLINE (#4242)8c07cf4fix(memory): bound retrieval queries before embedding (#4244)9ac1b52fix(zcode): skip providers that point at the Headroom proxy itself (#4413)023dd1bfix(logs): count omitted levels from dropped lines (#4141)89545fbfix(ccr): recognize client-owned MCP retrieval aliases (#4165)bebe24cfix(proxy): keep negative compression savings across restart (#4406)45dacc1fix(learn): anchor the managed block on its last start marker, append when no...5f308e1fix(proxy): skip memory tool injection on streamed OpenAI requests (#4451)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)