@qmediat.io/gemini-code-context-mcp 1.4.0 → 1.4.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +6 -0
- package/README.md +10 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -7,6 +7,12 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|
|
7
7
|
|
|
8
8
|
## [Unreleased]
|
|
9
9
|
|
|
10
|
+
## [1.4.1] — 2026-04-20
|
|
11
|
+
|
|
12
|
+
### Docs
|
|
13
|
+
|
|
14
|
+
- **README — "Upgrading to a new release"** subsection under *Installation methods*. Documents the `rm -rf ~/.npm/_npx` workaround for users on the `npx -y` install path who don't see a freshly-published version. Root cause: `npx -y` caches resolved packages, and npm's registry-metadata cache can keep serving the previously-installed version for a while after `npm publish`. Global-install and local-dev paths are unaffected and upgrade via `npm update -g` / `git pull && npm run build`.
|
|
15
|
+
|
|
10
16
|
## [1.4.0] — 2026-04-20
|
|
11
17
|
|
|
12
18
|
**Model taxonomy — allowlist-first category system.** The v1.2.0–v1.3.2 defence against `nano-banana-pro-preview` (image-gen) resolving to `latest-pro-thinking` was a reactive substring blocklist (`NON_TEXT_GEN_MARKERS = ['banana', 'lyria', 'research', ...]`). Every new non-text-gen family Google shipped under a `pro` / `flash` token required a patch release. v1.4.0 flips the model: each model ID is matched against an explicit rule set that assigns one of nine functional categories (`text-reasoning`, `text-fast`, `text-lite`, `image-generation`, `audio-generation`, `video-generation`, `embedding`, `agent`, `unknown`). Tools declare a required category; the resolver refuses to dispatch outside that set. Unknown families land in `unknown` and are excluded from every alias until the taxonomy is extended — forcing a conscious patch release rather than silent admission.
|
package/README.md
CHANGED
|
@@ -86,6 +86,16 @@ Full contract, category table, and examples: [`docs/models.md`](./docs/models.md
|
|
|
86
86
|
| **Global install** | `npm install -g @qmediat.io/gemini-code-context-mcp` → `"command": "gemini-code-context-mcp"` |
|
|
87
87
|
| **Local dev** | `git clone …; npm install; npm run build` → `"command": "node", "args": ["/path/to/dist/index.js"]` |
|
|
88
88
|
|
|
89
|
+
### Upgrading to a new release
|
|
90
|
+
|
|
91
|
+
If you use the **npx** method and a new version has been published but you're still getting the old one, clear the npx cache and restart your MCP host:
|
|
92
|
+
|
|
93
|
+
```bash
|
|
94
|
+
rm -rf ~/.npm/_npx
|
|
95
|
+
```
|
|
96
|
+
|
|
97
|
+
`npx -y` caches resolved packages, and npm's registry-metadata cache can keep serving the previously-installed version for a while after `npm publish`. The command above forces a fresh fetch on next MCP startup. Global-install and local-dev users upgrade via `npm update -g @qmediat.io/gemini-code-context-mcp` and `git pull && npm run build` respectively.
|
|
98
|
+
|
|
89
99
|
## How the caching works
|
|
90
100
|
|
|
91
101
|
```
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@qmediat.io/gemini-code-context-mcp",
|
|
3
|
-
"version": "1.4.
|
|
3
|
+
"version": "1.4.1",
|
|
4
4
|
"description": "MCP server that gives Claude Code persistent memory of your codebase, backed by Gemini's 2M-token context. Drop-in upgrade over the abandoned gemini-mcp-tool.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"mcp",
|