Skip to content

Context7 Platform -- Up-to-date docs for AI agents

chore(release): version packages (#3015)

github-actions[bot]f17ed6a455c4
diff --git a/.changeset/cli-token-refresh-commands.md b/.changeset/cli-token-refresh-commands.md
deleted file mode 100644
index d9b98d3a..00000000
--- a/.changeset/cli-token-refresh-commands.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-"ctx7": patch
----
-
-Fix `ctx7 library`, `ctx7 docs` and `ctx7 skills suggest` silently falling back to anonymous requests when the stored OAuth token expires, which surfaced misleading quota errors for authenticated users. `ctx7 generate` no longer forces a full interactive re-login when the token can be refreshed instead. All four commands now go through `getValidAccessToken()`, which refreshes expired credentials.
-
-A successful refresh also keeps the stored `refresh_token` when the server omits one from the response, as permitted by RFC 6749 §6. Previously the response was written verbatim, so the refresh token was dropped and the user was silently logged out at the next expiry.
diff --git a/.changeset/mcp-response-mode-auto.md b/.changeset/mcp-response-mode-auto.md
deleted file mode 100644
index cf581e59..00000000
--- a/.changeset/mcp-response-mode-auto.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-"@upstash/context7-mcp": patch
----
-
-Stop forcing `responseMode: "sse"` on the HTTP handler and use the SDK default `"auto"` instead. Forcing `"sse"` put every response on an SSE stream, and those streams were not released: concurrent upstream streams went from ~10 before v4.0.0 to over 5000, exhausting the gateway connection pool and returning 503 `reset reason: overflow` on `mcp.context7.com`. Traffic and latency were unchanged over that period, so the growth was not load.
-
-With `"auto"` a request is answered with a single JSON body unless a handler emits a related message before its result, which upgrades that one exchange to SSE. No tool emits progress today, so modern-protocol responses are now plain JSON. The 2025-era legacy fallback is constructed without a `responseMode` and still streams over SSE, so it is unaffected.
diff --git a/packages/cli/CHANGELOG.md b/packages/cli/CHANGELOG.md
index 5844ffc8..fe80c774 100644
--- a/packages/cli/CHANGELOG.md
+++ b/packages/cli/CHANGELOG.md
@@ -1,5 +1,13 @@
# Changelog
+## 0.5.8
+
+### Patch Changes
+
+- 91dea9f: Fix `ctx7 library`, `ctx7 docs` and `ctx7 skills suggest` silently falling back to anonymous requests when the stored OAuth token expires, which surfaced misleading quota errors for authenticated users. `ctx7 generate` no longer forces a full interactive re-login when the token can be refreshed instead. All four commands now go through `getValidAccessToken()`, which refreshes expired credentials.
+
+ A successful refresh also keeps the stored `refresh_token` when the server omits one from the response, as permitted by RFC 6749 §6. Previously the response was written verbatim, so the refresh token was dropped and the user was silently logged out at the next expiry.
+
## 0.5.7
### Patch Changes
diff --git a/packages/cli/package.json b/packages/cli/package.json
index 4edb5da2..d6c7aa65 100644
--- a/packages/cli/package.json
+++ b/packages/cli/package.json
@@ -1,6 +1,6 @@
{
"name": "ctx7",
- "version": "0.5.7",
+ "version": "0.5.8",
"description": "Context7 CLI - Fetch documentation context and configure Context7",
"type": "module",
"bin": {
diff --git a/packages/mcp/CHANGELOG.md b/packages/mcp/CHANGELOG.md
index 10d3b8f2..6127d302 100644
--- a/packages/mcp/CHANGELOG.md
+++ b/packages/mcp/CHANGELOG.md
@@ -1,5 +1,13 @@
# @upstash/context7-mcp
+## 4.0.1
+
+### Patch Changes
+
+- af7e4ad: Stop forcing `responseMode: "sse"` on the HTTP handler and use the SDK default `"auto"` instead. Forcing `"sse"` put every response on an SSE stream, and those streams were not released: concurrent upstream streams went from ~10 before v4.0.0 to over 5000, exhausting the gateway connection pool and returning 503 `reset reason: overflow` on `mcp.context7.com`. Traffic and latency were unchanged over that period, so the growth was not load.
+
+ With `"auto"` a request is answered with a single JSON body unless a handler emits a related message before its result, which upgrades that one exchange to SSE. No tool emits progress today, so modern-protocol responses are now plain JSON. The 2025-era legacy fallback is constructed without a `responseMode` and still streams over SSE, so it is unaffected.
+
## 4.0.0
### Major Changes
diff --git a/packages/mcp/package.json b/packages/mcp/package.json
index c09710e8..1b071f07 100644
--- a/packages/mcp/package.json
+++ b/packages/mcp/package.json
@@ -1,6 +1,6 @@
{
"name": "@upstash/context7-mcp",
- "version": "4.0.0",
+ "version": "4.0.1",
"mcpName": "io.github.upstash/context7",
"description": "MCP server for Context7",
"scripts": {