chore(plugin): bump engram to 4.5.2 for #164 rollout#195
Conversation
ОбзорОбновлена версия плагина в файле манифеста Изменения
Оценка сложности рецензирования кода🎯 1 (Trivial) | ⏱️ ~2 minutes Возможно связанные PR
Предлагаемые метки
Стихотворение
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
@coderabbitai review |
✅ Actions performedReview triggered.
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the version of the engram plugin to 4.5.2 in the plugin.json manifest. However, the review identifies critical issues including missing hooks and tools arrays required for the intended functionality, version inconsistencies across other project manifests and the marketplace configuration, and a potential conflict with the established hook strategy documented in the changelog.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@plugin/engram/.claude-plugin/plugin.json`:
- Line 3: Update CHANGELOG.md to add a new release section for version 4.5.2
(matching plugin.json which now has "version": "4.5.2"): insert a heading "##
[4.5.2] - 2026-04-XX" above the existing "[Unreleased]" section and add a "###
Fixed" bullet "- Stop-hook fix deployment (PR `#194`, commit 68baa0a)" following
Keep a Changelog formatting so the new entry appears immediately above the
Unreleased section.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: bfba2bac-14b7-4f30-b10c-03ba967991c5
📒 Files selected for processing (1)
plugin/engram/.claude-plugin/plugin.json
- keep PR-B plugin manifest version `5.0.0-alpha.1` (feature-track branch) - keep PR-B no-op `plugin/engram/hooks/stop.js` - absorb mainline rollout commits from PR #194/#195 without reintroducing stop-hook logic into the US3 PR-B branch Context: - main advanced via PR #194 (`68baa0a`) stop-hook fix and PR #195 (`c19a29c`) rollout bump to 4.5.2 - PR #196 intentionally supersedes that plugin state with the larger US3 cleanup branch, so conflicts are resolved in favor of the branch's v5-alpha plugin surface
1 participant
Summary
Follow-up rollout for resolved engram#164.
PR #194 (
68baa0a) fixed the stop hook crash in source code, but the user's local evidence shows Claude Code is still loading a stale cached plugin version (engram/4.5.0/hooks/stop.js). Claude refreshes cached plugin payloads by version, so this PR bumps the engram plugin version to force cache refresh and actual deployment of the already-merged stop-hook fix.Change
plugin/engram/.claude-plugin/plugin.json4.5.1→4.5.2Why this PR exists
Verified evidence from the local machine:
plugin/engram/hooks/stop.jscontains the fixed code (canonical transcript fallback +rl.on('error')guard)engram/4.5.0/hooks/stop.jswithout the fix4.2.0,4.4.0,4.5.0So the bug fix is merged in git, but not yet rolled out through the plugin versioning mechanism.
Issue
Follow-up to resolved engram#164 deployment gap.
Summary by CodeRabbit
Примечания к выпуску