headroom/plugins
Tejas Chopra 42c1ee2e77 chore: sync version state to released 0.31.0 to unblock release-please
Fixes the Release Please pipeline so it emits v0.32.0 — pip/Docker/npm are out of
sync because 0.32.0 was never actually released.

Root cause: #2175 (a fix(deps) PR) bumped pyproject + the RP manifest to 0.32.0
out-of-band, so release-please reads 0.32.0 as 'current' and computes the next
release as 0.33.0 (#1923), skipping 0.32.0 — which was never tagged/published
(last real release is v0.31.0). The plugin/marketplace manifests were left at
0.31.0, so version state was split-brained too.

Fix (mirrors #1916): realign every version-tracked file + the RP manifest to the
last real release, 0.31.0, via scripts/version-sync.py. release-please then sees
manifest=0.31.0 + releasable commits since v0.31.0 and rewrites its release PR to
'chore: release 0.32.0'; merging that tags v0.32.0 and fires release:published ->
PyPI + npm + Docker publish together, back in sync.

Versions only, no code change.
2026-07-16 21:06:01 -07:00
..
headroom-agent-hooks fix(release): sync all package versions to v0.31.0 (#1882) 2026-07-09 16:53:55 -05:00
headroom-oauth2 chore: remove committed node_modules + stray/internal markdown (repo hygiene) (#1528) 2026-06-27 23:32:54 -07:00
hermes fix(ccr): make headroom_retrieve a hash-only full-content lookup (#1532) 2026-06-28 10:32:43 -07:00
openclaw chore: sync version state to released 0.31.0 to unblock release-please 2026-07-16 21:06:01 -07:00
opencode docs(ccr): correct stale 5-minute TTL hints to 30 minutes (#2224) 2026-07-15 18:15:53 +00:00