Update dependency deno to v2.7.14

[renovate]

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
deno (source)	2.6.5 → 2.7.14

---

Additional fixes for Deno 2.7 compatibility

The following deprecated CLI flags have been removed from the test:deno:* scripts in package.json:

• --unstable-broadcast-channel: BroadcastChannel was stabilized in Deno 2.6.0, making this flag unnecessary. In Deno 2.7.x it causes an unknown unstable flag error.
• --unstable-byonm: "Bring Your Own node_modules" is now the default behavior in Deno 2.x, so this flag is deprecated and no longer needed.

The --unstable-kv flag is retained for the DenoKV storage tests, as Deno KV remains an unstable API.

---

Fix: upsertLocal() conflict under aggressive GC

Deno 2.7 runs the garbage collector more aggressively between async operations. upsertLocal previously relied solely on the doc cache to determine whether a local document existed. When the GC collected a returned RxDocument (whose only strong reference was via WeakRef in the cache), the FinalizationRegistry callback evicted the entire cache entry. On the next call to upsertLocal, the empty cache caused it to fall through to insertLocal, which then failed with a 409 conflict because the document still existed in storage.

upsertLocal now falls back to a getSingleDocument storage read when the cache has no entry for the given id. If the document is found in storage and is not deleted, it is updated via incrementalModify with the correct previous revision instead of attempting a conflicting insert.

---

Release Notes

[pubkey]

@copilot please analyze and propose a fix or improvement for this issue/PR.

Details

Important Reference (RxDB docs for LLMs)

Use the official RxDB docs here to align with architecture, plugins, storage abstractions, replication patterns, typings, and coding conventions:
https://rxdb.info/llms.txt

---

What to do (pick the right action based on what’s present)

Bug report with no test case

• Create a minimal failing test that reproduces the bug.
• Ensure the test fails on current main (or before your changes) and passes after the fix.
• Keep the test small and focused (one behavior).

Bug report with a test case already present but no fix

• Implement the minimal fix to make the existing test pass.
• Avoid unrelated refactors.
• Add additional assertions only if they clarify the intended behavior.

Regression (something used to work)

• Add/confirm a regression test that captures the previous correct behavior.
• Fix with the smallest change that restores compatibility.

Dependency version bump required

• Update the dependency versions as requested.
• Adjust code/types/tests to satisfy the new versions.
• If the bump requires breaking changes, document the reason and propose the smallest migration.

Types/TS errors

• Fix types in a way that preserves runtime behavior.
• Prefer stricter/correct typings over any or broad casts.
• Add a type-level or runtime test if the repo pattern supports it.

Docs-only or README mismatch

• Update docs/examples to match actual behavior.
• If docs reveal a bug, add a test and fix accordingly.

---

Output requirements

Please provide:

• A short root-cause explanation
• A unified diff patch (code + tests when applicable)
• Notes on edge-cases / compatibility
• If relevant: any migration notes

---

🚨 Author mention rule

If your solution:

• modifies the original author’s implementation, OR
• adds additional logic on top of the author's work, OR
• adds/changes tests related to the author's contribution,

then mention the original issue/PR author at the end of your response:

@ please review the proposed changes.

[Copilot]

@copilot please analyze and propose a fix or improvement for this issue/PR.

Details

...

Two improvements were needed alongside the version bump:

1. --unstable-broadcast-channel removed — BroadcastChannel was stabilized in Deno 2.6.0 (the previous version), so this flag is no longer needed and would cause an unknown unstable flag error in Deno 2.7.x.

2. --unstable-byonm removed — "Bring Your Own node_modules" is now the default behavior in Deno 2.x, so this flag is deprecated and unnecessary.

Both flags have been removed from all test:deno:* scripts in package.json. The --unstable-kv flag for DenoKV is kept since Deno KV remains unstable.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[pubkey]

@copilot the CI for this fails, please inspect the logs and fix.

[Copilot]

@copilot the CI for this fails, please inspect the logs and fix.

The CI failure was in test:deno:dexie — the test collection: should emit again when state changed consistently failed with a 409 conflict on upsertLocal.

Root cause: upsertLocal checked only the doc cache to decide whether to insert or update. Deno 2.7 runs the GC (and FinalizationRegistry callbacks) more aggressively between async operations. After insertLocal returned a document that the test discarded (no variable holding it), the GC collected the RxDocument object, triggering the FinalizationRegistry to evict the entry from cacheItemByDocId. By the time upsertLocal ran, the cache was empty, so it fell through to insertLocal — which then failed with a 409 because the document already existed in storage.

Fix (commit 908910b → new commit): upsertLocal now falls back to a storage read (getSingleDocument) when the cache has no entry for the id. If the document exists in storage (and is not deleted), it updates it via incrementalModify instead of trying to insert.