Skip to content

fix(deps): update all non-major dependencies - #497

Open
renovate-appwrite[bot] wants to merge 1 commit into
mainfrom
renovate/all-minor-patch
Open

renovate-appwrite[bot] wants to merge 1 commit into
mainfrom
renovate/all-minor-patch

Conversation

@renovate-appwrite

@renovate-appwrite renovate-appwrite Bot commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence Type Update Pending
@elevenlabs/elevenlabs-js 2.60.0 → 2.78.0 age confidence dependencies minor 2.79.0
@fal-ai/client (source) 1.10.1 → 1.11.0 age confidence dependencies minor
@langchain/core (source) 1.2.4 → 1.4.1 age confidence dependencies minor 1.5.0 (+1)
@langchain/openai (source) 1.5.5 → 1.8.4 age confidence dependencies minor 1.8.5
@qdrant/js-client-rest (source) 1.18.0 → 1.20.0 age confidence dependencies minor
@types/node (source) 22.20.4 → 22.20.5 age confidence devDependencies patch
@types/node (source) 22.20.1 → 22.20.5 age confidence devDependencies patch
@upstash/vector (source) 1.2.3 → 1.2.4 age confidence dependencies patch
Appwrite [0.21.2,0.22.0) → [0.21.2,0.27.0] age confidence nuget minor
actions/setup-dotnet v6.0.0 → v6.1.0 age confidence action minor
actions/setup-node v7.0.0 → v7.1.0 age confidence action minor
actions/setup-python v7.0.0 → v7.1.0 age confidence action minor
appwrite 0.4.0 → 0.23.0 age confidence dependencies minor 0.24.0
appwrite '>= 27.0.0', '< 28.0.0' → '>= 27.0.0', '< 28.4.1' age confidence minor
appwrite/sdk-for-swift from: "13.2.2" → from: "13.3.0" age confidence minor
dart-lang/setup-dart v1.7.2 → v1.8.2 age confidence action minor
dodopayments 2.54.0 → 2.62.0 age confidence dependencies minor 2.63.1 (+1)
dotenv (changelog) '>= 2.8.1', '< 3.0.0' → '>= 2.8.1', '< 3.2.1' age confidence minor
drizzle-orm (source) 0.45.3 → 0.45.4 age confidence dependencies patch
esbuild ^0.25.12 → ^0.28.0 age confidence overrides minor
github.com/appwrite/sdk-for-go v0.13.1 → v0.17.0 age confidence require minor
github.com/open-runtimes/types-for-go/v4 v4.0.8 → v4.0.11 age confidence require patch
go 1.26.11 → 1.27.4 age confidence uses-with minor
json (changelog) '>= 2.7.6', '< 3.0.0' → '>= 2.7.6', '< 3.1.1' age confidence minor
langchain (source) 1.5.4 → 1.6.6 age confidence dependencies minor 1.6.7
markdown-table 3.0.3 → 3.1.0 age confidence dependencies minor
meilisearch >=0.30.0,<0.31.0 → >=0.43.0,<0.44.0 age confidence minor
meilisearch ^0.40.0 → ^0.63.0 age confidence dependencies minor
meilisearch ^0.35.0 → ^0.63.0 age confidence dependencies minor
mongodb 6.21.0 → 6.22.0 age confidence dependencies minor
node-appwrite (source) 29.0.0 → 29.4.0 age confidence dependencies minor
node-appwrite (source) 29.1.0 → 29.4.0 age confidence dependencies minor
node-appwrite (source) 31.1.0 → 31.2.0 age confidence dependencies minor 31.3.0
nodemailer (source) 10.2.1 → 10.5.0 age confidence dependencies minor 10.6.1 (+1)
openai >=0.27.8,<0.28.0 → >=0.28.1,<0.29.0 age confidence minor
openai-php/client ^0.6.4 → ^0.22.0 age confidence require minor
openruntimes 1.0.2 → 1.0.3 age confidence dependencies patch
prettier (source) 3.9.6 → 3.10.1 age confidence devDependencies minor
prettier (source) 3.9.9 → 3.10.1 age confidence devDependencies minor
prettier (source) 3.9.10 → 3.10.1 age confidence devDependencies minor
python 3.11 → 3.15 age confidence uses-with minor
replicate ^0.29.4 → ^0.34.0 age confidence dependencies minor
ruby (source) 3.1 → 3.4 age confidence uses-with minor 3.4.13
ruby/setup-ruby v1.320.0 → v1.338.0 age confidence action minor v1.343.0 (+4)
serde_json 1.0.149 → 1.0.154 age confidence dependencies patch
shivammathur/setup-php 2.37.2 → 2.40.0 age confidence action minor
tokio (source) 1.53.3 → 1.54.1 age confidence dependencies minor
typescript (source) 5.4.5 → 5.9.3 age confidence dependencies minor
com.google.code.gson:gson 2.10.1 → 2.15.0 age confidence dependencies minor
com.meilisearch.sdk:meilisearch-java 0.11.2 → 0.22.1 age confidence dependencies minor
io.appwrite:sdk-for-kotlin 4.0.0 → 4.1.0 age confidence dependencies minor
io.appwrite:sdk-for-kotlin 12.2.1 → 12.3.0 age confidence dependencies minor

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

elevenlabs/elevenlabs-js (@​elevenlabs/elevenlabs-js)

v2.78.0

Compare Source

What's Changed

Full Changelog: elevenlabs/elevenlabs-js@v2.77.0...v2.78.0

v2.77.0

Compare Source

What's Changed

Full Changelog: elevenlabs/elevenlabs-js@v2.76.0...v2.77.0

v2.76.0

Compare Source

What's Changed

Full Changelog: elevenlabs/elevenlabs-js@v2.75.0...v2.76.0

v2.75.0

Compare Source

What's Changed

Full Changelog: elevenlabs/elevenlabs-js@v2.74.0...v2.75.0

v2.74.0

Compare Source

What's Changed

Full Changelog: elevenlabs/elevenlabs-js@v2.73.0...v2.74.0

v2.73.0

Compare Source

What's Changed

New Contributors

Full Changelog: elevenlabs/elevenlabs-js@v2.72.0...v2.73.0

v2.72.0

Compare Source

What's Changed

Full Changelog: elevenlabs/elevenlabs-js@v2.71.0...v2.72.0

v2.71.0

Compare Source

What's Changed

Full Changelog: elevenlabs/elevenlabs-js@v2.70.0...v2.71.0

v2.70.0

Compare Source

What's Changed

Full Changelog: elevenlabs/elevenlabs-js@v2.69.0...v2.70.0

v2.69.0

Compare Source

What's Changed

New Contributors

Full Changelog: elevenlabs/elevenlabs-js@v2.68.0...v2.69.0

v2.68.0

Compare Source

What's Changed

Full Changelog: elevenlabs/elevenlabs-js@v2.67.0...v2.68.0

v2.67.0

Compare Source

What's Changed

Full Changelog: elevenlabs/elevenlabs-js@v2.66.0...v2.67.0

v2.66.0

Compare Source

What's Changed

New Contributors

Full Changelog: elevenlabs/elevenlabs-js@v2.65.0...v2.66.0

v2.65.0

Compare Source

What's Changed

Full Changelog: elevenlabs/elevenlabs-js@v2.64.0...v2.65.0

v2.64.0

Compare Source

What's Changed

Full Changelog: elevenlabs/elevenlabs-js@v2.63.0...v2.64.0

v2.63.0

Compare Source

What's Changed

Full Changelog: elevenlabs/elevenlabs-js@v2.62.0...v2.63.0

v2.62.0

Compare Source

What's Changed

Full Changelog: elevenlabs/elevenlabs-js@v2.61.0...v2.62.0

v2.61.0

Compare Source

What's Changed

Full Changelog: elevenlabs/elevenlabs-js@v2.60.0...v2.61.0

fal-ai/fal-js (@​fal-ai/client)

v1.11.0

Compare Source

langchain-ai/langchainjs (@​langchain/core)

v1.4.1

Compare Source

Patch Changes

v1.4.0

Compare Source

Minor Changes
  • #​12178 01e5f2d Thanks @​thushanth-bengre-langchain! - feat(core): add decision models

    • Add @langchain/core/decisions with BaseDecisionModel, a Runnable that answers typed Noul, Choice, Score, and Box questions about text, messages, or JSON state
    • Add question and answer types, parseQuestions, and parseClassifierResponse for providers
    • Type invoke answers from the questions asked, including Choice labels, and reject provider responses that leave a question unanswered or answer it with the wrong type or label
Patch Changes

v1.3.7

Compare Source

Patch Changes
  • #​12120 a4fb396 Thanks @​thushanth-bengre-langchain! - feat(core): add a standard refusal content block and ModelRefusalError

    Model refusals from OpenAI, Anthropic, and Gemini now appear as a refusal content block in message.contentBlocks. JSON, tool-call, and structured output parsers throw ModelRefusalError (from @langchain/core/errors) when the model refuses, instead of a generic parsing error.

v1.3.6

Compare Source

Patch Changes
  • #​12140 f054550 Thanks @​hntrl! - Stop streamEvents v2 from hanging or leaking an unhandled rejection when aborted, and from throwing its own AbortError when the consumer breaks early.

v1.3.5

Compare Source

Patch Changes
  • #​10961 674b755 Thanks @​hntrl! - fix(prompts): enforce maximum prompt template nesting depth

    Add recursion depth guards for mustache template parsing and dict prompt template traversal to prevent stack-exhaustion DoS from deeply nested attacker-controlled templates.

  • #​12108 fb61799 Thanks @​casparb! - fix(core): end the tool() run when its signal is already aborted

v1.3.4

Compare Source

Patch Changes
  • #​12104 e006308 Thanks @​hntrl! - Export omitPayload from @langchain/core/tracers/tracer_langchain, a TracePolicy processor that records an empty payload while keeping the run.

  • #​12102 6d157ae Thanks @​hntrl! - LangChainTracer now still sends and ends a run when its trace policy's processInputs or processOutputs throws, with that payload dropped and the error set, instead of skipping the run or leaving it pending in LangSmith.

v1.3.3

Compare Source

Patch Changes
  • #​11567 d92aba6 Thanks @​hntrl! - Add tracePolicy to RunnableSequence. Its processInputs/processOutputs shape only what LangChainTracer sends to LangSmith for the sequence's own run. Batched sequence runs now each record their own output.

v1.3.2

Compare Source

Patch Changes

v1.3.1

Compare Source

Patch Changes
  • #​12026 178af31 Thanks @​eliornl! - fix(core): deliver callbacks once to a handler registered twice by merged configs

    Merging two runnable configs that both carry the same callback handler, as happens when an agent's streamEvents() runs inside a LangGraph node with tracing on, registered that handler twice, so it received every callback twice: every streamed chunk arrived twice. The configured callback manager now keeps each handler once, in order, including a handler passed as a plain object of methods that merged configs wrapped twice.

  • #​12042 50343ba Thanks @​sera-wi! - fix(core): include node metadata in Graph.toJSON() output when set, matching Python

  • #​12048 304d190 Thanks @​sera-wi! - fix(core): escape drawMermaid node metadata labels and leave out object values, so metadata with brackets or objects no longer breaks Mermaid parsing

v1.3.0

Compare Source

Minor Changes
  • #​11986 2caf64d Thanks @​richardscarrott! - feat: stream tool-call args as tool-call-delta slices

    Tool-call and server-tool-call args now stream as tool-call-delta events, which carry only the new slice of the args, instead of block-delta snapshots of the args so far. A large tool call now costs about the same bytes on the wire as the same length of text.

    • This covers the compat bridge (any model that only implements _streamResponseChunks), the OpenAI-compatible converter (OpenAI Completions, Groq, Mistral, IBM, OpenRouter, Perplexity, DeepSeek, Fireworks, Together AI and xAI Completions), OpenAI and xAI Responses, Anthropic (client and server tool calls) and Bedrock Converse. Google and Ollama still send one complete snapshot per call.
    • A tool call's id, name and index go on content-block-start, which carries no args. An id or name that arrives later reaches consumers on content-block-finish.
    • If you read raw events and their block-delta fields.args mid-stream, or write agent stream transformers that do, read tool-call-delta instead. await stream, .toolCalls and the assembled message are unchanged.
    • Upgrade your clients first. Older clients mishandle tool-call-delta. You need @langchain/langgraph-sdk 1.12.6 or later; @langchain/react, @langchain/vue, @langchain/svelte or @langchain/angular 1.2.6 or later; and langchain-core 1.6.13 or later for Python clients.
    • To hold back, pin @langchain/core below 1.3.0. That also keeps you on @langchain/openai, @langchain/anthropic, @langchain/aws and @langchain/xai versions that send snapshots.

v1.2.20

Compare Source

Patch Changes
  • #​11922 d71c542 Thanks @​richardscarrott! - feat(core): add midConversationSystemMessages and midConversationTools to ModelProfile. They say whether a chat model sends a system message after the first turn in place, and whether it can add a tool through a message rather than the request's tool list. Either way the prompt prefix before it stays unchanged.

v1.2.19

Compare Source

Patch Changes
  • #​11982 5af4684 Thanks @​richardscarrott! - feat(core): read tool-call-delta in ChatModelStream

    • ChatModelStream appends tool-call-delta slices to a tool call's args, and still replaces them on block-delta
    • It ignores delta types it doesn't recognize instead of throwing Unknown delta type

v1.2.18

Compare Source

Patch Changes
  • #​11956 93d62b0 Thanks @​hntrl! - Require langsmith >=0.11.0 to include the restored NullableHeaders type declarations.

  • #​11822 d3e6fe6 Thanks @​dqbd! - Add explicit agent address support to LangChainTracer, inherit project and address destinations together, and delegate default destination resolution to the LangSmith SDK.

  • #​11150 cea15cf Thanks @​mdnanocom! - fix(core): defer tool call chunk collapsing in AIMessageChunk to fix O(n²) streaming aggregation

    AIMessageChunk eagerly re-ran collapseToolCallChunks in its constructor on every streamed delta concat, re-parsing all accumulated tool args each time — O(n²) over a stream, which can block the event loop for seconds on long tool-call streams. Collapsing now runs lazily, once, on first read of tool_calls / invalid_tool_calls.

v1.2.17

Compare Source

Patch Changes
  • #​11849 b1d9c7a Thanks @​KyleCodes! - Preserve runtime context in ambient runnable config across tool calls, nested runnables, and streaming.

v1.2.16

Compare Source

Patch Changes

v1.2.14

Compare Source

Patch Changes
  • #​11771 bbed273 Thanks @​thushanth-bengre-langchain! - Add fileMimeTypes to ModelProfile so models can advertise the MIME types they accept as generic file inputs. OpenAI Responses API models now report the file types input_file supports;
    Chat Completions profiles are unchanged.

v1.2.13

Compare Source

Patch Changes
  • #​11714 a83dfb1 Thanks @​ccurme! - Abbreviate long tool-call IDs when formatting chat messages as strings, keeping original messages unchanged.

v1.2.12

Compare Source

Patch Changes

[v1.2.11](https://redirect.github.com/langchain-ai

[!IMPORTANT]
✂ PR body was truncated to here.

@renovate-appwrite renovate-appwrite Bot added the dependencies Pull requests that update a dependency file label Nov 9, 2026
@appwrite

appwrite Bot commented Nov 9, 2026 •

Copy link
Copy Markdown

Code review

Commit Status Tier Verdict Details
50320ee Reviewed Reviewed 🟡 B · Needs changes before merging 💬 Commented View review

Previously reported findings remain open, including template build failures and dependency-audit issues.

This pull request refreshes dependency versions across the Node.js, Python, Ruby, Go, Rust, .NET, JVM, PHP, Swift, and Bun templates. It also updates the language and action versions used by the build and dependency-audit workflows.

Fix with agent prompt
### Issue 1
node-typescript/sync-with-meilisearch/package-lock.json:52
**Meilisearch 0.62 renames the imported constructor**

The 0.62 client exports `Meilisearch`, not `MeiliSearch`: `npm run build` in this template now fails with TS2724. The same stale named import also prevents module loading in `node/sync-with-meilisearch/src/main.js` and `bun/sync-with-meilisearch/src/main.ts`.

### Issue 2
node-typescript/sync-with-qdrant/package-lock.json:25
**Qdrant 1.20 removes the `search` method**

The client removed `search` in 1.19 in favor of `query`, but `node-typescript/sync-with-qdrant/src/main.ts:38` still calls `client.search`. I ran `npm run build` in this template; it fails with TS2339, and the search endpoint cannot work with this client version.

### Issue 3
node-typescript/sync-with-qdrant/package-lock.json:25
**Qdrant 1.20 requires a newer Node runtime**

The locked client requires Node >=22 (and its `undici` dependency requires >=20.18.1), while this template still declares Node >=18.17 in `package.json` and documents Node 18 in its README. The advertised runtime is outside the supported range; raise the runtime requirement or keep a client compatible with Node 18.

### Issue 4
node-typescript/sync-with-meilisearch/package-lock.json:52
**Meilisearch 0.62 excludes the documented Node 18 runtime**

This client declares Node `^20.19.0 || >=22.12.0`, but the template still declares Node >=18.17 in `package.json` and documents Node 18 in its README. The new lock therefore no longer matches the template's advertised runtime; align the runtime requirement or use a compatible client.

### Issue 5
dotnet/starter/StarterTemplate.csproj:9
**Keep the .NET Appwrite range open to compatible patches**

The inclusive upper bound stops at 0.27.0, so compatible patch releases such as 0.27.1 are excluded. The repository dependency rule requires allowing compatible patch/minor updates while excluding the next breaking version.

### Issue 6
ruby/starter/Gemfile:3
**Keep the Ruby Appwrite range open to compatible patches**

`< 28.4.1` excludes 28.4.1 and all later 28.4.x patch releases; the same cap was added in `ruby/sync_with_meilisearch/Gemfile:3`. The repository dependency rule requires allowing compatible patch/minor updates while excluding the next breaking version.

### Issue 7
ruby/whatsapp-with-vonage/Gemfile:3-4
**Ruby json and dotenv ranges exclude the next compatible patches**

These upper bounds exclude the next patch releases (json 3.1.1 and dotenv 3.2.1) rather than the next breaking versions. That prevents compatible fixes from being selected and conflicts with the repository dependency rule.

### Issue 8
node/rag-with-langchain/package-lock.json:140
**LangChain OpenAI 1.8.0 drops the declared Node 20 support**

This lock resolves `@langchain/openai` 1.8.0, whose engine requires Node >=22, while `node/rag-with-langchain/package.json` still declares support for `>=20.0.0` (and its transitive `openai` 7.50.0 has the same Node floor). A deployment using Node 20, which the package manifest permits, is now outside the supported runtime range.

### Issue 9
rust/starter/Cargo.toml:12
**Appwrite SDK requires a newer Rust toolchain**

Appwrite 0.22.0 declares `rust-version = 1.85`, but this template and `.github/workflows/build.yml` use Rust 1.83. The Rust build job will reject this dependency; update the toolchain floor or use an SDK that supports 1.83.

### Issue 10
python/sync_with_meilisearch/requirements.txt:2
**Meilisearch 0.43 no longer supports Python 3.9**

Meilisearch 0.43 declares `Requires-Python: >=3.10`, while this template advertises Python 3.9 and the CI Python 3.9 job installs its requirements. Pip cannot resolve this dependency for the declared runtime, so the template build fails; keep a Python 3.9-compatible client or raise the runtime requirement.

### Issue 11
php/prompt-chatgpt/composer.json:6
**OpenAI PHP client 0.22 requires PHP 8.2**

OpenAI PHP client 0.22.0 requires PHP `^8.2.0`, but this template still declares and documents PHP 8.0. Composer installation on PHP 8.0 or 8.1 will fail; align the supported runtime or use a compatible client version.

### Issue 12
node-typescript/sync-with-qdrant/package-lock.json:41
**Qdrant locks an undici version with high-severity advisories**

`npm audit` flags undici 7.29.1 with high-severity advisories, including remote denial-of-service and cache/TLS issues. Both `node/sync-with-qdrant` and `node-typescript/sync-with-qdrant` lock this version through the updated Qdrant client, so both templates inherit the vulnerable dependency.

### Issue 13
.github/workflows/audit.yml:170
**Update govulncheck for the Go 1.27 toolchain**

With this Go version, the pinned `govulncheck@v1.1.4` crashes while scanning `go/discord-command-bot` (`panic: unexpected expr: *ast.KeyValueExpr` in `golang.org/x/tools`), so the Go audit job cannot complete. I reproduced it by running `go run golang.org/x/vuln/cmd/govulncheck@v1.1.4 ./...` with Go 1.27.3; use a scanner version compatible with this toolchain or keep the job on a supported Go version.

### Issue 14
node/sync-with-qdrant/package-lock.json:23
**Qdrant 1.20 removes the search API used by this template**

After `npm ci`, the locked 1.20 client has no `search` method (`query` is available), but `node/sync-with-qdrant/src/main.js:38` still calls it. Every `/search` request therefore throws `TypeError: client.search is not a function` instead of returning results.

### Issue 15
node/sync-with-qdrant/package-lock.json:32
**Qdrant 1.20 raises this template's Node requirement to 22**

The client now requires Node >=22, while `node/sync-with-qdrant/package.json` allows >=18.17.0 and the README advertises Node 18. Deployments on that documented runtime are outside the dependency's supported engine range; align the runtime requirement or use a compatible client.

### Issue 16
java/starter/deps.gradle:2
**Appwrite Kotlin SDK is pinned to one release**

This exact pin blocks compatible patch and minor releases for the Java starter; `kotlin/starter/deps.gradle:2` repeats the same constraint. The repository dependency rule requires allowing compatible updates while excluding the next breaking version, so use a bounded Gradle version range.

### Issue 17
kotlin/sync-with-meilisearch/deps.gradle:2-4
**JVM client dependencies are pinned to exact versions**

All three exact versions block compatible patch/minor releases in this template. The repository dependency rule requires bounded constraints that admit compatible updates while excluding the next breaking version.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.
Walkthrough (20)
File Change
.github/workflows/audit.yml Refreshes action and language versions used by dependency-audit jobs.
.github/workflows/build.yml Refreshes action and language versions used by template build jobs.
.github/workflows/markdown-table-workflow/package-lock.json Updates the markdown-table lockfile entry.
bun/sync-with-meilisearch/{package.json,bun.lock} Updates the Meilisearch dependency and Bun lockfile.
dotnet/starter/StarterTemplate.csproj Updates the Appwrite NuGet package range.
go/{discord-command-bot,starter}/{go.mod,go.sum} Updates the Open Runtimes Go types and Go Appwrite SDK dependencies.
java/starter/deps.gradle Updates the Appwrite Kotlin SDK version used by the Java starter.
kotlin/{starter,sync-with-meilisearch}/deps.gradle Updates Appwrite and Meilisearch JVM dependencies.
node-typescript/postgres-with-drizzle/{package.json,package-lock.json} Updates the esbuild override and refreshes TypeScript, Drizzle, and related lockfile dependencies.
node-typescript/sync-with-meilisearch/{package.json,package-lock.json} Updates Meilisearch, Appwrite, and TypeScript dependencies.
node-typescript/sync-with-qdrant/package-lock.json Updates Qdrant and related lockfile dependencies.
node-typescript/*/package-lock.json Refreshes Node type definitions, Prettier, and Appwrite dependencies in TypeScript templates.
node/*/package-lock.json Refreshes lockfile versions for Appwrite and several template-specific SDKs and utilities.
node/generate-with-replicate/package.json Updates the Replicate SDK version constraint.
node/sync-with-meilisearch/package.json Updates the Meilisearch SDK version constraint.
php/prompt-chatgpt/composer.json Updates the OpenAI PHP client constraint.
python/{prompt_chatgpt,sync_with_meilisearch}/requirements.txt Updates the OpenAI and Meilisearch Python constraints.
ruby/{starter,sync_with_meilisearch,whatsapp-with-vonage}/Gemfile Updates Ruby dependency version ranges.
rust/starter/{Cargo.toml,Cargo.lock} Updates the Appwrite Rust SDK and related crate lockfile entries.
swift/starter/Package.swift Updates the minimum Swift SDK version.
Still open from earlier reviews (17)

Reviewed 50320ee

Tip

Comment @appwrite review to re-run, or mention @appwrite with a question.

@appwrite appwrite Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Tier B · 2 blocking findings to address. Summary

"version": "0.40.0",
"resolved": "https://registry.npmjs.org/meilisearch/-/meilisearch-0.40.0.tgz",
"integrity": "sha512-BoRhQMr2mBFLEeCfsvPluksGb01IaOiWvV3Deu3iEY+yYJ4jdGTu+IQi5FCjKlNQ7/TMWSN2XUToSgvH1tj0BQ==",
"version": "0.62.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Meilisearch 0.62 renames the imported constructor

The 0.62 client exports Meilisearch, not MeiliSearch: npm run build in this template now fails with TS2724. The same stale named import also prevents module loading in node/sync-with-meilisearch/src/main.js and bun/sync-with-meilisearch/src/main.ts.

Prompt To Fix With AI
This is a comment left during a code review.
Path: node-typescript/sync-with-meilisearch/package-lock.json
Line: 52

Comment:
**Meilisearch 0.62 renames the imported constructor**

The 0.62 client exports `Meilisearch`, not `MeiliSearch`: `npm run build` in this template now fails with TS2724. The same stale named import also prevents module loading in `node/sync-with-meilisearch/src/main.js` and `bun/sync-with-meilisearch/src/main.ts`.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

🟠 Major · bug · Reply if this doesn't apply.

"version": "1.18.0",
"resolved": "https://registry.npmjs.org/@qdrant/js-client-rest/-/js-client-rest-1.18.0.tgz",
"integrity": "sha512-/0dqX5uV9chC1DnYSnU4gNMrDqse/pt6hHg3Rqqpl5isH7xl1xSNvffjzBoxycDD79luWn7Ho6Rh/61sOs5DNw==",
"version": "1.20.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Qdrant 1.20 removes the search method

The client removed search in 1.19 in favor of query, but node-typescript/sync-with-qdrant/src/main.ts:38 still calls client.search. I ran npm run build in this template; it fails with TS2339, and the search endpoint cannot work with this client version.

Prompt To Fix With AI
This is a comment left during a code review.
Path: node-typescript/sync-with-qdrant/package-lock.json
Line: 25

Comment:
**Qdrant 1.20 removes the `search` method**

The client removed `search` in 1.19 in favor of `query`, but `node-typescript/sync-with-qdrant/src/main.ts:38` still calls `client.search`. I ran `npm run build` in this template; it fails with TS2339, and the search endpoint cannot work with this client version.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

🟠 Major · bug · Reply if this doesn't apply.

"version": "1.18.0",
"resolved": "https://registry.npmjs.org/@qdrant/js-client-rest/-/js-client-rest-1.18.0.tgz",
"integrity": "sha512-/0dqX5uV9chC1DnYSnU4gNMrDqse/pt6hHg3Rqqpl5isH7xl1xSNvffjzBoxycDD79luWn7Ho6Rh/61sOs5DNw==",
"version": "1.20.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Qdrant 1.20 requires a newer Node runtime

The locked client requires Node >=22 (and its undici dependency requires >=20.18.1), while this template still declares Node >=18.17 in package.json and documents Node 18 in its README. The advertised runtime is outside the supported range; raise the runtime requirement or keep a client compatible with Node 18.

Prompt To Fix With AI
This is a comment left during a code review.
Path: node-typescript/sync-with-qdrant/package-lock.json
Line: 25

Comment:
**Qdrant 1.20 requires a newer Node runtime**

The locked client requires Node >=22 (and its `undici` dependency requires >=20.18.1), while this template still declares Node >=18.17 in `package.json` and documents Node 18 in its README. The advertised runtime is outside the supported range; raise the runtime requirement or keep a client compatible with Node 18.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

🟡 Minor · bug · Reply if this doesn't apply.

"version": "0.40.0",
"resolved": "https://registry.npmjs.org/meilisearch/-/meilisearch-0.40.0.tgz",
"integrity": "sha512-BoRhQMr2mBFLEeCfsvPluksGb01IaOiWvV3Deu3iEY+yYJ4jdGTu+IQi5FCjKlNQ7/TMWSN2XUToSgvH1tj0BQ==",
"version": "0.62.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Meilisearch 0.62 excludes the documented Node 18 runtime

This client declares Node ^20.19.0 || >=22.12.0, but the template still declares Node >=18.17 in package.json and documents Node 18 in its README. The new lock therefore no longer matches the template's advertised runtime; align the runtime requirement or use a compatible client.

Prompt To Fix With AI
This is a comment left during a code review.
Path: node-typescript/sync-with-meilisearch/package-lock.json
Line: 52

Comment:
**Meilisearch 0.62 excludes the documented Node 18 runtime**

This client declares Node `^20.19.0 || >=22.12.0`, but the template still declares Node >=18.17 in `package.json` and documents Node 18 in its README. The new lock therefore no longer matches the template's advertised runtime; align the runtime requirement or use a compatible client.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

🟡 Minor · bug · Reply if this doesn't apply.

</PropertyGroup>
<ItemGroup>
<PackageReference Include="Appwrite" Version="[0.21.2,0.22.0)" />
<PackageReference Include="Appwrite" Version="[0.21.2,0.27.0]" />

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Keep the .NET Appwrite range open to compatible patches

The inclusive upper bound stops at 0.27.0, so compatible patch releases such as 0.27.1 are excluded. The repository dependency rule requires allowing compatible patch/minor updates while excluding the next breaking version.

Prompt To Fix With AI
This is a comment left during a code review.
Path: dotnet/starter/StarterTemplate.csproj
Line: 9

Comment:
**Keep the .NET Appwrite range open to compatible patches**

The inclusive upper bound stops at 0.27.0, so compatible patch releases such as 0.27.1 are excluded. The repository dependency rule requires allowing compatible patch/minor updates while excluding the next breaking version.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

🟡 Minor · maintainability · Reply if this doesn't apply.

Comment thread ruby/starter/Gemfile
source "https://rubygems.org"

gem 'appwrite', '>= 27.0.0', '< 28.0.0'
gem 'appwrite', '>= 27.0.0', '< 28.4.1'

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Keep the Ruby Appwrite range open to compatible patches

< 28.4.1 excludes 28.4.1 and all later 28.4.x patch releases; the same cap was added in ruby/sync_with_meilisearch/Gemfile:3. The repository dependency rule requires allowing compatible patch/minor updates while excluding the next breaking version.

Prompt To Fix With AI
This is a comment left during a code review.
Path: ruby/starter/Gemfile
Line: 3

Comment:
**Keep the Ruby Appwrite range open to compatible patches**

`< 28.4.1` excludes 28.4.1 and all later 28.4.x patch releases; the same cap was added in `ruby/sync_with_meilisearch/Gemfile:3`. The repository dependency rule requires allowing compatible patch/minor updates while excluding the next breaking version.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

🟡 Minor · maintainability · Reply if this doesn't apply.

Comment on lines +3 to +4
gem 'json', '>= 2.7.6', '< 3.1.1'
gem 'dotenv', '>= 2.8.1', '< 3.2.1'

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ruby json and dotenv ranges exclude the next compatible patches

These upper bounds exclude the next patch releases (json 3.1.1 and dotenv 3.2.1) rather than the next breaking versions. That prevents compatible fixes from being selected and conflicts with the repository dependency rule.

Prompt To Fix With AI
This is a comment left during a code review.
Path: ruby/whatsapp-with-vonage/Gemfile
Line: 3-4

Comment:
**Ruby json and dotenv ranges exclude the next compatible patches**

These upper bounds exclude the next patch releases (json 3.1.1 and dotenv 3.2.1) rather than the next breaking versions. That prevents compatible fixes from being selected and conflicts with the repository dependency rule.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

🟡 Minor · maintainability · Reply if this doesn't apply.

@renovate-appwrite
renovate-appwrite Bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from a4a99a6 to d3895e5 Compare November 11, 2026 14:17

@appwrite appwrite Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Tier B · See the inline comments. Summary

"version": "1.5.5",
"resolved": "https://registry.npmjs.org/@langchain/openai/-/openai-1.5.5.tgz",
"integrity": "sha512-wX7dwb9z4nf5FHXlIl/X2mk08pzonvRHCt1D4+s1zXLP0duYDC95j7dulPIQJ6fmhbyYQc9Ki8mEhY/D1lB8kw==",
"version": "1.8.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LangChain OpenAI 1.8.0 drops the declared Node 20 support

This lock resolves @langchain/openai 1.8.0, whose engine requires Node >=22, while node/rag-with-langchain/package.json still declares support for >=20.0.0 (and its transitive openai 7.50.0 has the same Node floor). A deployment using Node 20, which the package manifest permits, is now outside the supported runtime range.

Prompt To Fix With AI
This is a comment left during a code review.
Path: node/rag-with-langchain/package-lock.json
Line: 140

Comment:
**LangChain OpenAI 1.8.0 drops the declared Node 20 support**

This lock resolves `@langchain/openai` 1.8.0, whose engine requires Node >=22, while `node/rag-with-langchain/package.json` still declares support for `>=20.0.0` (and its transitive `openai` 7.50.0 has the same Node floor). A deployment using Node 20, which the package manifest permits, is now outside the supported runtime range.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

🟡 Minor · bug · Reply if this doesn't apply.

@renovate-appwrite
renovate-appwrite Bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from cf12c03 to f96a41c Compare November 13, 2026 14:16

@appwrite appwrite Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟠 Tier C · 4 blocking findings to address. Summary

Comment thread rust/starter/Cargo.toml Outdated

[dependencies]
appwrite = "0.4.0"
appwrite = "0.22.0"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Appwrite SDK requires a newer Rust toolchain

Appwrite 0.22.0 declares rust-version = 1.85, but this template and .github/workflows/build.yml use Rust 1.83. The Rust build job will reject this dependency; update the toolchain floor or use an SDK that supports 1.83.

Prompt To Fix With AI
This is a comment left during a code review.
Path: rust/starter/Cargo.toml
Line: 12

Comment:
**Appwrite SDK requires a newer Rust toolchain**

Appwrite 0.22.0 declares `rust-version = 1.85`, but this template and `.github/workflows/build.yml` use Rust 1.83. The Rust build job will reject this dependency; update the toolchain floor or use an SDK that supports 1.83.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

🟠 Major · bug · Reply if this doesn't apply.

@@ -1,2 +1,2 @@
appwrite>=23.0.0,<24.0.0
meilisearch>=0.30.0,<0.31.0
meilisearch>=0.43.0,<0.44.0

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Meilisearch 0.43 no longer supports Python 3.9

Meilisearch 0.43 declares Requires-Python: >=3.10, while this template advertises Python 3.9 and the CI Python 3.9 job installs its requirements. Pip cannot resolve this dependency for the declared runtime, so the template build fails; keep a Python 3.9-compatible client or raise the runtime requirement.

Prompt To Fix With AI
This is a comment left during a code review.
Path: python/sync_with_meilisearch/requirements.txt
Line: 2

Comment:
**Meilisearch 0.43 no longer supports Python 3.9**

Meilisearch 0.43 declares `Requires-Python: >=3.10`, while this template advertises Python 3.9 and the CI Python 3.9 job installs its requirements. Pip cannot resolve this dependency for the declared runtime, so the template build fails; keep a Python 3.9-compatible client or raise the runtime requirement.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

🟠 Major · bug · Reply if this doesn't apply.

"require": {
"php": ">=8.0.0",
"openai-php/client": "^0.6.4",
"openai-php/client": "^0.22.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OpenAI PHP client 0.22 requires PHP 8.2

OpenAI PHP client 0.22.0 requires PHP ^8.2.0, but this template still declares and documents PHP 8.0. Composer installation on PHP 8.0 or 8.1 will fail; align the supported runtime or use a compatible client version.

Prompt To Fix With AI
This is a comment left during a code review.
Path: php/prompt-chatgpt/composer.json
Line: 6

Comment:
**OpenAI PHP client 0.22 requires PHP 8.2**

OpenAI PHP client 0.22.0 requires PHP `^8.2.0`, but this template still declares and documents PHP 8.0. Composer installation on PHP 8.0 or 8.1 will fail; align the supported runtime or use a compatible client version.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

🟠 Major · bug · Reply if this doesn't apply.

}
},
"node_modules/@qdrant/js-client-rest/node_modules/undici": {
"version": "7.29.1",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Qdrant locks an undici version with high-severity advisories

npm audit flags undici 7.29.1 with high-severity advisories, including remote denial-of-service and cache/TLS issues. Both node/sync-with-qdrant and node-typescript/sync-with-qdrant lock this version through the updated Qdrant client, so both templates inherit the vulnerable dependency.

Prompt To Fix With AI
This is a comment left during a code review.
Path: node-typescript/sync-with-qdrant/package-lock.json
Line: 41

Comment:
**Qdrant locks an undici version with high-severity advisories**

`npm audit` flags undici 7.29.1 with high-severity advisories, including remote denial-of-service and cache/TLS issues. Both `node/sync-with-qdrant` and `node-typescript/sync-with-qdrant` lock this version through the updated Qdrant client, so both templates inherit the vulnerable dependency.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

🟠 Major · security · Reply if this doesn't apply.

@renovate-appwrite
renovate-appwrite Bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 5473a2c to de7cff5 Compare November 14, 2026 06:23

@appwrite appwrite Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Tier B · See the inline comments. Summary

Comment thread .github/workflows/audit.yml Outdated
- uses: actions/setup-go@b7ad1dad31e06c5925ef5d2fc7ad053ef454303e # v7.0.0
with:
go-version: "1.26.11"
go-version: "1.27.3"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Update govulncheck for the Go 1.27 toolchain

With this Go version, the pinned govulncheck@v1.1.4 crashes while scanning go/discord-command-bot (panic: unexpected expr: *ast.KeyValueExpr in golang.org/x/tools), so the Go audit job cannot complete. I reproduced it by running go run golang.org/x/vuln/cmd/govulncheck@v1.1.4 ./... with Go 1.27.3; use a scanner version compatible with this toolchain or keep the job on a supported Go version.

Prompt To Fix With AI
This is a comment left during a code review.
Path: .github/workflows/audit.yml
Line: 170

Comment:
**Update govulncheck for the Go 1.27 toolchain**

With this Go version, the pinned `govulncheck@v1.1.4` crashes while scanning `go/discord-command-bot` (`panic: unexpected expr: *ast.KeyValueExpr` in `golang.org/x/tools`), so the Go audit job cannot complete. I reproduced it by running `go run golang.org/x/vuln/cmd/govulncheck@v1.1.4 ./...` with Go 1.27.3; use a scanner version compatible with this toolchain or keep the job on a supported Go version.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

🟡 Minor · bug · Reply if this doesn't apply.

@renovate-appwrite
renovate-appwrite Bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 543c9a4 to 778c6bf Compare November 17, 2026 06:26

@appwrite appwrite Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Tier B · 1 blocking finding to address. Summary

"version": "1.18.0",
"resolved": "https://registry.npmjs.org/@qdrant/js-client-rest/-/js-client-rest-1.18.0.tgz",
"integrity": "sha512-/0dqX5uV9chC1DnYSnU4gNMrDqse/pt6hHg3Rqqpl5isH7xl1xSNvffjzBoxycDD79luWn7Ho6Rh/61sOs5DNw==",
"version": "1.20.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Qdrant 1.20 removes the search API used by this template

After npm ci, the locked 1.20 client has no search method (query is available), but node/sync-with-qdrant/src/main.js:38 still calls it. Every /search request therefore throws TypeError: client.search is not a function instead of returning results.

Prompt To Fix With AI
This is a comment left during a code review.
Path: node/sync-with-qdrant/package-lock.json
Line: 23

Comment:
**Qdrant 1.20 removes the search API used by this template**

After `npm ci`, the locked 1.20 client has no `search` method (`query` is available), but `node/sync-with-qdrant/src/main.js:38` still calls it. Every `/search` request therefore throws `TypeError: client.search is not a function` instead of returning results.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

🟠 Major · bug · Reply if this doesn't apply.

"engines": {
"node": ">=18.17.0",
"pnpm": ">=8"
"node": ">=22.0.0"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Qdrant 1.20 raises this template's Node requirement to 22

The client now requires Node >=22, while node/sync-with-qdrant/package.json allows >=18.17.0 and the README advertises Node 18. Deployments on that documented runtime are outside the dependency's supported engine range; align the runtime requirement or use a compatible client.

Prompt To Fix With AI
This is a comment left during a code review.
Path: node/sync-with-qdrant/package-lock.json
Line: 32

Comment:
**Qdrant 1.20 raises this template's Node requirement to 22**

The client now requires Node >=22, while `node/sync-with-qdrant/package.json` allows >=18.17.0 and the README advertises Node 18. Deployments on that documented runtime are outside the dependency's supported engine range; align the runtime requirement or use a compatible client.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

🟡 Minor · bug · Reply if this doesn't apply.

@renovate-appwrite
renovate-appwrite Bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from 0d394aa to 3cca11c Compare November 20, 2026 06:26

@appwrite appwrite Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Tier B · See the inline comments. Summary

Comment thread java/starter/deps.gradle
@@ -1,3 +1,3 @@
dependencies {
implementation 'io.appwrite:sdk-for-kotlin:12.2.1'
implementation 'io.appwrite:sdk-for-kotlin:12.3.0'

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Appwrite Kotlin SDK is pinned to one release

This exact pin blocks compatible patch and minor releases for the Java starter; kotlin/starter/deps.gradle:2 repeats the same constraint. The repository dependency rule requires allowing compatible updates while excluding the next breaking version, so use a bounded Gradle version range.

Prompt To Fix With AI
This is a comment left during a code review.
Path: java/starter/deps.gradle
Line: 2

Comment:
**Appwrite Kotlin SDK is pinned to one release**

This exact pin blocks compatible patch and minor releases for the Java starter; `kotlin/starter/deps.gradle:2` repeats the same constraint. The repository dependency rule requires allowing compatible updates while excluding the next breaking version, so use a bounded Gradle version range.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

🟡 Minor · maintainability · Reply if this doesn't apply.

Comment on lines +2 to +4
implementation 'io.appwrite:sdk-for-kotlin:4.1.0'
implementation 'com.meilisearch.sdk:meilisearch-java:0.22.1'
implementation 'com.google.code.gson:gson:2.15.0'

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

JVM client dependencies are pinned to exact versions

All three exact versions block compatible patch/minor releases in this template. The repository dependency rule requires bounded constraints that admit compatible updates while excluding the next breaking version.

Prompt To Fix With AI
This is a comment left during a code review.
Path: kotlin/sync-with-meilisearch/deps.gradle
Line: 2-4

Comment:
**JVM client dependencies are pinned to exact versions**

All three exact versions block compatible patch/minor releases in this template. The repository dependency rule requires bounded constraints that admit compatible updates while excluding the next breaking version.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

🟡 Minor · maintainability · Reply if this doesn't apply.

@renovate-appwrite
renovate-appwrite Bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 1202057 to 5f4c94a Compare November 21, 2026 06:23
@renovate-appwrite
renovate-appwrite Bot force-pushed the renovate/all-minor-patch branch from 5f4c94a to 50320ee Compare November 21, 2026 14:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants