chore(supabase): stop tracking the CLI's .temp/cli-latest cache
This commit is contained in:
1 parent
f99b4a581f
commit
1312b366b1
3 files changed
+6
-2
No files matched your search
+2
-1
@@ -56,7 +56,8 @@ graphify-out/
|
||||
.claude/deploy/PENDING.json
|
||||
.claude/deploy/NEXT.sh
|
||||
|
||||
# Supabase CLI local state (written by supabase start / db reset)
|
||||
# Supabase CLI local state (written by supabase start / db reset, version checks): never
|
||||
# tracked; the CLI recreates it. supabase/.env.* is covered by the .env.* rule above.
|
||||
supabase/.branches/
|
||||
supabase/.temp/
|
||||
|
||||
|
||||
@@ -10,6 +10,10 @@ Versions follow [Semantic Versioning](https://semver.org/).
|
||||
|
||||
- **Worker TLS: rustls 0.23.45 → 0.23.46** (`Cargo.lock` only, through `ureq` 3.4.2): RUSTSEC-2026-0346 (session values' `Debug` printed TLS secrets), 0347 (ECH rejection), 0348 (Brotli certificate decompression), 0349 (unauthenticated ServerHello pinning the next key exchange group). None reached the worker as configured (ring provider without ML-KEM groups, no ECH, no `brotli` feature, sessions never printed); the bump removes them anyway. No API or feature change; the patch also fixes `StreamOwned` flushing and surfaces a connection's fatal error on the next write. `cargo deny check advisories` clean.
|
||||
|
||||
### Fixed (maintenance after R2, 2026-10-14)
|
||||
|
||||
- `supabase/.temp/cli-latest` (the Supabase CLI's version-check cache) is no longer tracked: it had been committed before the `supabase/.temp/` ignore rule existed, so every CLI run dirtied the tree. The local copy stays; the ignore rules already cover `.temp/`, `.branches/` and `supabase/.env.*`.
|
||||
|
||||
### Changed (Rust R2, domain core, 2026-10-14)
|
||||
|
||||
- **The application's domain rules run in Rust** (`crates/core`, through the wasm facade and `@faunosteo/core-wasm`): sheet, report and archive contracts with the Zod semantics reproduced, the 21 sheet integrity rules and the publish check, the sheet index, the v2 → v3 migration, the rebase on the loaded sheet, the sheet snapshot, the layered archive reading, the editor's click chain and reducers, the findings and vertebra rules, report creation and the observation list operations. Consumers switched: the editor, the pickers, the store, the draft restore, the PDF import (after the engine's byte scan) and export (snapshot), the Supabase publish gate (fails closed). The module (340 KB gzip) loads only on the sheet pages; sign-in, the `/app` space and Home never request it. Without `'wasm-unsafe-eval'` in the CSP the editor shows a degraded notice with a retry and leaves the session's draft untouched (DEPLOY.md: set the keyword before deploying an R2 image; R2 images are never built on the VPS).
|
||||
|
||||
@@ -1 +0,0 @@
|
||||
v2.120.0
|
||||
Reference in new issue
Block a user