Skip to content

chore(deps): lock file maintenance - #502

Open
renovate-appwrite[bot] wants to merge 1 commit into
mainfrom
renovate/lock-file-maintenance
Open

renovate-appwrite[bot] wants to merge 1 commit into
mainfrom
renovate/lock-file-maintenance

Conversation

@renovate-appwrite

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Update Change
lockFileMaintenance All locks refreshed

Warning

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

🔧 This Pull Request updates lock files to use the latest dependency versions.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Only on Monday (* * * * 1)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

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

appwrite Bot commented Nov 16, 2026 •

Copy link
Copy Markdown

Code review

Commit Status Tier Verdict Details
bf7e956 Reviewed Reviewed 🟡 B · Needs changes before merging 🛑 Changes requested View review

The lockfiles add dependencies whose declared Node requirements exceed the runtimes supported by the affected templates, alongside unresolved Qdrant findings.

This change refreshes dependency lockfiles across the Node, TypeScript, Rust, and PHP templates. It updates package resolutions for Appwrite SDKs and other direct and transitive dependencies, along with lockfile metadata.

1 of 54 changed files was too large to include in full.

Findings (2)
Finding Where
🟠 Firebase database dependency now requires Node 24 node/push-notification-with-fcm/package-lock.json:72
🟠 LangChain OpenAI adapter now requires Node 22 node/rag-with-langchain/package-lock.json:150
Fix with agent prompt
### Issue 1
node/push-notification-with-fcm/package-lock.json:72
**Firebase database dependency now requires Node 24**

The README documents this function on Node 18, but the refreshed `@firebase/database` and `@firebase/database-compat` packages both declare Node `>=24.12.0`; they are pulled in by `firebase-admin`, imported in `src/utils.js:1`. This puts the documented runtime outside the dependency's supported range and can make startup fail on Node 18.

### Issue 2
node/rag-with-langchain/package-lock.json:150
**LangChain OpenAI adapter now requires Node 22**

This template's `package.json` allows Node `>=20`, but this adapter and its locked `openai` 7.62.0 dependency require Node `>=22`. `src/main.js:4,61` imports and uses `ChatOpenAI`/`OpenAIEmbeddings`, so Node 20 deployments accepted by the template are now outside the SDKs' supported runtime and can fail when serving prompts.

### Issue 3
node-typescript/sync-with-qdrant/package-lock.json:25
**Qdrant 1.20 removes the `search()` method this template uses**

The 1.20 client no longer exposes `search()`; the prior 1.18 declaration did. Running `npm run build` now fails at `src/main.ts:38`, and the JavaScript sibling template calls the same method in its `/search` route, which will fail at runtime too.

### Issue 4
node/sync-with-qdrant/package-lock.json:23
**Qdrant 1.20 exceeds the template's Node 18 runtime**

This client now declares Node `>=22` and pulls Undici 7 (Node `>=20.18.1`), while this template's package manifest accepts Node `>=18.17.0` and its README documents Node 18. Deployments on that documented runtime are outside the supported range for the Qdrant client; the TypeScript sibling lock has the same upgrade.

### Issue 5
node/sync-with-qdrant/package-lock.json:882
**Undici 7.29.1 has known high-severity vulnerabilities**

`npm audit` in `node/sync-with-qdrant` reports this locked Undici version as affected by multiple advisories, including high-severity denial-of-service issues; the vulnerable dependency is used by the Qdrant client. The TypeScript sibling lock also resolves Undici 7.29.1.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.
Walkthrough (5)
File Change
.github/workflows/markdown-table-workflow/package-lock.json Refreshes the markdown-table workflow dependency.
node/**/package-lock.json Refreshes dependency resolutions across the JavaScript templates, including Appwrite and project-specific packages.
node-typescript/**/package-lock.json Refreshes dependency resolutions across the TypeScript templates.
rust/starter/Cargo.lock Refreshes the Rust starter's locked crates.
php/starter/composer.lock Updates Composer lockfile metadata.
Still open from earlier reviews (3)

Reviewed bf7e956

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 · 3 blocking findings 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() method this template uses

The 1.20 client no longer exposes search(); the prior 1.18 declaration did. Running npm run build now fails at src/main.ts:38, and the JavaScript sibling template calls the same method in its /search route, which will fail at runtime too.

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 this template uses**

The 1.20 client no longer exposes `search()`; the prior 1.18 declaration did. Running `npm run build` now fails at `src/main.ts:38`, and the JavaScript sibling template calls the same method in its `/search` route, which will fail at runtime too.

---

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 exceeds the template's Node 18 runtime

This client now declares Node >=22 and pulls Undici 7 (Node >=20.18.1), while this template's package manifest accepts Node >=18.17.0 and its README documents Node 18. Deployments on that documented runtime are outside the supported range for the Qdrant client; the TypeScript sibling lock has the same upgrade.

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 exceeds the template's Node 18 runtime**

This client now declares Node `>=22` and pulls Undici 7 (Node `>=20.18.1`), while this template's package manifest accepts Node `>=18.17.0` and its README documents Node 18. Deployments on that documented runtime are outside the supported range for the Qdrant client; the TypeScript sibling lock has the same upgrade.

---

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.

"resolved": "https://registry.npmjs.org/undici/-/undici-6.29.1.tgz",
"integrity": "sha512-EvRlUt/QqAEvXdQeRMYUfwOQsfzpDztykrG2owGEE/rBOBoYv9uF39ZzsNDh4lTFHhTr2XOZjKkYgueD12ZmGA==",
"version": "7.29.1",
"resolved": "https://registry.npmjs.org/undici/-/undici-7.29.1.tgz",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Undici 7.29.1 has known high-severity vulnerabilities

npm audit in node/sync-with-qdrant reports this locked Undici version as affected by multiple advisories, including high-severity denial-of-service issues; the vulnerable dependency is used by the Qdrant client. The TypeScript sibling lock also resolves Undici 7.29.1.

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

Comment:
**Undici 7.29.1 has known high-severity vulnerabilities**

`npm audit` in `node/sync-with-qdrant` reports this locked Undici version as affected by multiple advisories, including high-severity denial-of-service issues; the vulnerable dependency is used by the Qdrant client. The TypeScript sibling lock also resolves Undici 7.29.1.

---

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/lock-file-maintenance branch from 174fb95 to bf7e956 Compare November 20, 2026 14:17
@renovate-appwrite

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: bun/starter/bun.lock
Resolving dependencies
Resolved, downloaded and extracted [17]
error: No version matching "1.4.5" found for specifier "bun-types" (blocked by minimum-release-age: 259200 seconds)
error: bun-types@1.4.5 failed to resolve

File name: bun/sync-with-meilisearch/bun.lock
Resolving dependencies
Resolved, downloaded and extracted [134]
error: No version matching "1.4.5" found for specifier "bun-types" (blocked by minimum-release-age: 259200 seconds)
error: bun-types@1.4.5 failed to resolve

File name: bun/sync-with-qdrant/bun.lock
Resolving dependencies
Resolved, downloaded and extracted [109]
error: No version matching "1.4.5" found for specifier "bun-types" (blocked by minimum-release-age: 259200 seconds)
error: bun-types@1.4.5 failed to resolve

File name: bun/whatsapp-with-vonage/bun.lock
Resolving dependencies
Resolved, downloaded and extracted [66]
error: No version matching "1.4.5" found for specifier "bun-types" (blocked by minimum-release-age: 259200 seconds)
error: bun-types@1.4.5 failed to resolve

@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

},
"engines": {
"node": ">=20.0.0"
"node": ">=24.12.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.

Firebase database dependency now requires Node 24

The README documents this function on Node 18, but the refreshed @firebase/database and @firebase/database-compat packages both declare Node >=24.12.0; they are pulled in by firebase-admin, imported in src/utils.js:1. This puts the documented runtime outside the dependency's supported range and can make startup fail on Node 18.

Prompt To Fix With AI
This is a comment left during a code review.
Path: node/push-notification-with-fcm/package-lock.json
Line: 72

Comment:
**Firebase database dependency now requires Node 24**

The README documents this function on Node 18, but the refreshed `@firebase/database` and `@firebase/database-compat` packages both declare Node `>=24.12.0`; they are pulled in by `firebase-admin`, imported in `src/utils.js:1`. This puts the documented runtime outside the dependency's supported range and can make startup fail on Node 18.

---

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": ">=20"
"node": ">=22"

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 adapter now requires Node 22

This template's package.json allows Node >=20, but this adapter and its locked openai 7.62.0 dependency require Node >=22. src/main.js:4,61 imports and uses ChatOpenAI/OpenAIEmbeddings, so Node 20 deployments accepted by the template are now outside the SDKs' supported runtime and can fail when serving prompts.

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

Comment:
**LangChain OpenAI adapter now requires Node 22**

This template's `package.json` allows Node `>=20`, but this adapter and its locked `openai` 7.62.0 dependency require Node `>=22`. `src/main.js:4,61` imports and uses `ChatOpenAI`/`OpenAIEmbeddings`, so Node 20 deployments accepted by the template are now outside the SDKs' supported runtime and can fail when serving prompts.

---

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.

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