Re-vendor the Greptile CLI at 3.5.2 - #7
Merged
Merged
Conversation
3.5.1 never reached npm: its publish landed during an npm registry incident on 2026-09-03 and the tarball was never stored, so `npm install greptile@3.5.1` failed while Homebrew and the GitHub release served it fine. 3.5.2 republishes those bytes. The vendored bundle is `npm pack greptile@3.5.2`'s `dist/greptile.js`, sha256 f5fac84b4c5d8a68d6419f543008d076f7e3b5066a424cb0c1aa77c458080275 — the same digest the GitHub release asset carries and the Homebrew formula pins, so all four channels agree on one artifact again.
 The reviewable changes appear safe to merge, with no actionable defects identified.
|
![greptile-apps-staging[bot]](https://avatars.githubusercontent.com/in/919028?s=60&v=4){kind=small}
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Brings the plugin's bundled CLI from 3.5.0 to 3.5.2 and bumps the plugin to 1.2.3.
Why 3.5.2 and not 3.5.1
3.5.1 never reached npm. Its publish landed during an npm registry incident on 2026-09-03: the version document and the
latestdist-tag were written, but the packument was never rebuilt and the tarball was never stored, sonpm install greptile@3.5.1failed withETARGETfor a full day. Homebrew and the GitHub release were unaffected, since neither goes through npm. 3.5.2 republishes the same content and npm has since healed both versions.Re-vendoring at 3.5.1 was therefore impossible while it was broken — CLI Check resolves the bundle with
npm pack, which had nothing to fetch.One artifact, four channels
The vendored
greptile.mjsisdist/greptile.jsfromnpm pack greptile@3.5.2, taken from the registry rather than a local build, perRELEASING.mdstep 6:That digest is identical across all four channels — the npm tarball, the
greptileai/cliv3.5.2 release asset, thesha256the Homebrew formula pins, and this file. Verified by fetching each independently.Checks
node plugins/greptile/scripts/greptile.mjs --version→3.5.2, run fromscripts/, which has no siblingpackage.json🤖 Generated with Claude Code
https://claude.ai/code/session_019FX8tWGjHhJTXBExyqWYnj