Repository navigation
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should fix [policy] — this bumps the anchor file, but
action.yml:378'sheadroom_versiondefault is still"0.37.0"and isn't touched by this PR.Per this file's own header (lines 3–5 above) and
docs/headroom.md's "Version pinning" section: "the version this action actually installs lives in action.yml'sheadroom_versioninput default... when this file's version bumps, update action.yml's default to match in the same PR; neither pair wired together automatically."requirements-headroom.txtis explicitly "never installed from directly" — it exists only so Dependabot can track the pin. So as it stands this PR changes nothing about what the action actually installs; the two pins are left out of sync exactly as the comment warns against.Worth noting for whoever does the
action.ymlsync: upstream's v0.40.0 release notes list two ⚠ BREAKING CHANGES ("readHEADROOM_LICENSE, make usage reporting opt-in"; "dropcrewaiextra, remove chromadb from lockfile") despite Dependabot classifying this assemver-minor(headroom-ai is pre-1.0, so a second-position bump can still be breaking). Thecrewaiextra isn't the[proxy]extra this repo installs, but the license/usage-reporting change is proxy-wide and worth a look before trusting the new default blindly.If you'd like me to fix this, comment: