Skip to content

chore(deps): lock file maintenance - #26

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

🔧 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.

@appwrite

appwrite Bot commented Nov 16, 2026 •

Copy link
Copy Markdown

🟡 Tier B · Needs changes before merging

The two existing open findings remain unresolved: Biome CI fails, and Astro's Node floor still exceeds the package's advertised support range.

Refreshes the npm lockfile with current versions of Astro, Biome, and transitive dependencies. The refreshed dependency graph also adds and removes package entries as dependencies are deduplicated.

Verdict New comments Fixed Still open
💬 Commented 0 0 2

Note

Not approving while a bug finding is open: Astro 7.4.12 raises the Node floor above 22.12

Fix with agent prompt
### Issue 1
package-lock.json:473
**Biome 2.6.8 leaves the required format check failing**

With this locked version, `npx biome ci` reports that `biome.jsonc` still uses the 2.5.9 schema and fails on formatting differences in six tracked docs/workflows, matching the failed check. The lock update therefore leaves required CI red; update the Biome config/output or keep a compatible CLI version.

### Issue 2
package-lock.json:2694
**Astro 7.4.12 raises the Node floor above 22.12**

Astro 7.3.3 in the base lock declared Node `>=22.12.0`, but this version requires `>=22.23.4`; the package still advertises Node 22.12 in `package.json` and tests/builds the example at that floor in `.github/workflows/ci.yml`. Since `src/cache/provider.ts` imports Astro's runtime `astro/cache/provider-utils`, the supported Node range now includes an unsupported Astro/Node combination; align the supported floor and CI or keep an Astro resolution compatible with 22.12.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.
📂 Walkthrough · 1
File Change
package-lock.json Updates locked dependency versions and adjusts transitive dependency entries.
⏳ Still open from earlier reviews · 2

Reviewed 2303457 · Details · Comment @appwrite review to re-run, or mention @appwrite with a question.

Comment thread package-lock.json

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Line 473 · GitHub does not show this file's diff, so this comment is on the file.

Biome 2.6.8 leaves the required format check failing

With this locked version, npx biome ci reports that biome.jsonc still uses the 2.5.9 schema and fails on formatting differences in six tracked docs/workflows, matching the failed check. The lock update therefore leaves required CI red; update the Biome config/output or keep a compatible CLI version.

Prompt To Fix With AI
This is a comment left during a code review.
Path: package-lock.json
Line: 473

Comment:
**Biome 2.6.8 leaves the required format check failing**

With this locked version, `npx biome ci` reports that `biome.jsonc` still uses the 2.5.9 schema and fails on formatting differences in six tracked docs/workflows, matching the failed check. The lock update therefore leaves required CI red; update the Biome config/output or keep a compatible CLI version.

---

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

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

Comment thread package-lock.json

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Line 2694 · GitHub does not show this file's diff, so this comment is on the file.

Astro 7.4.12 raises the Node floor above 22.12

Astro 7.3.3 in the base lock declared Node >=22.12.0, but this version requires >=22.23.4; the package still advertises Node 22.12 in package.json and tests/builds the example at that floor in .github/workflows/ci.yml. Since src/cache/provider.ts imports Astro's runtime astro/cache/provider-utils, the supported Node range now includes an unsupported Astro/Node combination; align the supported floor and CI or keep an Astro resolution compatible with 22.12.

Prompt To Fix With AI
This is a comment left during a code review.
Path: package-lock.json
Line: 2694

Comment:
**Astro 7.4.12 raises the Node floor above 22.12**

Astro 7.3.3 in the base lock declared Node `>=22.12.0`, but this version requires `>=22.23.4`; the package still advertises Node 22.12 in `package.json` and tests/builds the example at that floor in `.github/workflows/ci.yml`. Since `src/cache/provider.ts` imports Astro's runtime `astro/cache/provider-utils`, the supported Node range now includes an unsupported Astro/Node combination; align the supported floor and CI or keep an Astro resolution compatible with 22.12.

---

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.

@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 A · See the inline comments. Summary

@renovate-appwrite
renovate-appwrite Bot force-pushed the renovate/lock-file-maintenance branch from 6a4f713 to 2303457 Compare November 17, 2026 06:50

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants