Upstash
upstash.comDatabase
$
npx @buildinternet/releases get upstashEnterprise access tokens now validated at MCP server
↗This release1 featureNew capabilitiesAI-tallied from the release notescontext7 · @upstash/context7-mcp@3.2.2
Enterprise-Managed Auth (id-jag) access tokens are now validated at the MCP server, enabling MCP clients to authenticate to Context7 through an enterprise IdP such as Okta.
GitHub API errors now show status and detail
↗This release3 enhancementsImprovements to existing features1 fixBug fixesAI-tallied from the release notescontext7 · ctx7@0.5.3
GitHub API failures during ctx7 setup now show the HTTP status and error body (e.g. "HTTP 403: API rate limit exceeded") instead of the opaque "GitHub API error". A 403/429 hint suggests gh auth login or setting GITHUB_TOKEN.
Node 18 support restored; startup crash fixed
↗This release1 fixBug fixesAI-tallied from the release notescontext7 · @upstash/context7-mcp@3.2.1
Restored Node 18 support by pinning undici to ^6.26.0 and commander to ^13.1.0, resolving a "File is not defined" crash on startup.
Workflow runs now support multiple labels with OR filtering
↗This release1 featureNew capabilities1 enhancementImprovements to existing featuresAI-tallied from the release notesWorkflow runs now support multiple labels via string | string[] on client.trigger and context.invoke, with log, DLQ, and cancel filters accepting arrays to match runs that have any of the given labels. The context.labels: string[] field replaces the deprecated context.label, and workflow run logs now expose a labels field.