chore: bump server + plugin to v4.4.0 (Phase 6 release)#172
Conversation
Phase 6 release ceremony for the v4.4.0 train. Bumps the unified engram-server + plugin version after the 5-PR train completed: #167 — Phase B-1 plumbing tenant (loom integration) #168 — Phase 2 obs.MeterFor helper + loom OTel wiring #169 — Phase 3 4 loom_* tools + CLI worker with allowlist #170 — Phase 4 server-side gRPC proto extensions + soft-delete reaper #171 — Phase 5 daemon serverevents bridge for real OnProjectRemoved e2e Per Constitution §15 the daemon version and plugin version must move together, so this commit bumps: - cmd/engram/main.go daemonVersion "v4.3.0" → "v4.4.0" Reported to gRPC Initialize + logged in structured output. - plugin/engram/.claude-plugin/plugin.json version "4.3.0" → "4.4.0" Drives Claude Code plugin cache invalidation on /reload-plugins. Without this bump the marketplace update would not be detected. No behaviour change, no test change. Release notes + git tag + gh release + marketplace sync land in subsequent steps.
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 4 minutes and 20 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
| // daemonVersion is the string reported to gRPC Initialize and used in | ||
| // structured logs. Tracks Constitution §15 unified engram + plugin version. | ||
| const daemonVersion = "v4.3.0" | ||
| const daemonVersion = "v4.4.0" |
There was a problem hiding this comment.
The version bump to v4.4.0 is correct, but it leaves several stale version references in the documentation and comments. Specifically, the package documentation at the top of this file (lines 1 and 7) and the comments in cmd/engram/wiring.go (line 19) still refer to v4.3.0. Additionally, the comment on line 83 regarding named-pipe support being deferred to v4.4.0 should be updated as this is now the current version.
1 participant
What
Bumps the unified engram-server + plugin version from v4.3.0 → v4.4.0 per Constitution §15.
Why
Phase 6 release ceremony for the v4.4.0 train. All 5 preceding PRs have already merged to main:
f011e22b3dc577ff57fecd324f01b340017Per Constitution §15 the daemon version and plugin version move together as a single release unit. Without the plugin.json bump, Claude Code plugin cache would serve stale files on
/reload-pluginsand the marketplace would not detect the update.Changes
cmd/engram/main.go—daemonVersionconstant"v4.3.0" → "v4.4.0"plugin/engram/.claude-plugin/plugin.json—"version": "4.3.0" → "4.4.0"No behaviour change, no test change. Full ceremony continues after merge:
git tag v4.4.0gh release create v4.4.0 --title "v4.4.0" --notes-file docs/release-notes/v4.4.0.mdthebtf/engram-marketplaceso the plugin index picks up the new version.