Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

chore(pi): gentle-engram 0.3.0 shipped to npm without a GitHub release; pinned plugin users had no update signal and setup could not reach it

Open
  • Is something wrong?
#1,706 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
go
Domain
release

Research direction

Start with the three proposed solutions and map each to its surface: the plugin release flow that should create a pi-v0.3.0 GitHub release, the checker list in gentle-ai update (see Gentleman-Programming/gentle-ai#1902 for the adjacent report), and the setup-pin strings in the core release that engram setup pi reads. Read docs/packages.md for the pin/reconciliation rules, and check which repo owns each change — some work is cross-repository. Done means a published plugin version has an announcement channel, the update command reports the gentle-engram pin, and the core tag carrying a new setup pin is ordered at or before the npm publish.

Written by the indexing model from the issue text.

Description

status:needs-review type:chore
🔍 Problem Description

[email protected] was published to npm at 2026-10-07T04:40:11Z (dist-tags.latest=0.3.0), but no GitHub release exists for it (pi-v0.3.0 → not found; the latest plugin release remains "gentle-engram v0.2.0", 2026-10-01). Users following the documented update flows had no signal that 0.3.0 existed, and no canonical flow reached it:

  • gentle-ai upgrade upgrades "managed tool binaries only. Agent configs are preserved — no install or sync is performed" (verified against the released CLI), so it never touches the pi plugin pin.
  • gentle-shell update --extensions proxies to pi update --extensions, and per the pi docs (docs/packages.md): "Versioned npm specifications are pinned … package updates reconcile the checkout but do not move a configured ref." With the exact pin npm:[email protected], reconciliation correctly kept 0.2.0 — the pin moved only after a manual gentle-shell install npm:[email protected].
  • gentle-ai update (checker) lists gentle-ai / engram / gga / opencode-subagent-statusline; it does not list the gentle-engram pi plugin pin (adjacent: Gentleman-Programming/gentle-ai#1902).

Additionally, the setup-pin alignment for 0.3.0 (#1702, merged 2026-10-07T05:02Z) landed after the v3.2.1 core tag (2026-10-07T03:13Z): the released 3.2.1 binary contains no 0.3.0 reference in its setup strings (only the 0.1.x legacy names), so engram setup pi on the current core release could not migrate users to 0.3.0 either. In that window, every documented path left pinned users on 0.2.0.

💡 Proposed Solution
  1. Publish a GitHub release (tag pi-v0.3.0, even short) for plugin npm releases, so the announcement channel and release notes exist for each plugin version.
  2. Surface the gentle-engram plugin pin in gentle-ai update (or an --extensions surface), distinguished from core tool checks (relates to Gentleman-Programming/gentle-ai#1902).
  3. When the setup pin moves to a new gentle-engram version, tag the core that carries the migration at or before the npm publish (or state in the npm release which core version carries it), so engram setup pi reaches the new version within the same release window.
Environment

Linux; engram 3.2.1 (Homebrew); gentle-ai 4.0.0; gentle-pi 4.0.0; pi pinned child 1.0.0; plugin was gentle-engram 0.2.0 → manually upgraded to 0.3.0 via gentle-shell install npm:[email protected] (the only working path in that window).

Observations are separated from inferences; no ids, paths, tokens, or settings shared.

Dominant language
Go
Stars
7.1k
Forks
729
Avg merge
11h 17m
Merged PRs (30d)
334

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Gentleman-Programming/engram

All issues in Gentleman-Programming/engram

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.