Skip to content

chore(deps): bump tauri from 2.11.0 to 2.11.1 in /src-tauri#6

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/src-tauri/tauri-2.11.1
Closed

chore(deps): bump tauri from 2.11.0 to 2.11.1 in /src-tauri#6
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/src-tauri/tauri-2.11.1

Conversation

@dependabot
Copy link
Copy Markdown

@dependabot dependabot Bot commented on behalf of github May 7, 2026

Bumps tauri from 2.11.0 to 2.11.1.

Release notes

Sourced from tauri's releases.

tauri-cli v2.11.1

Fetching advisory database from `https://github.com/RustSec/advisory-db.git`
      Loaded 1067 security advisories (from /home/runner/.cargo/advisory-db)
    Updating crates.io index
    Scanning Cargo.lock for vulnerabilities (1088 crate dependencies)
Crate:     atk
Version:   0.18.2
Warning:   unmaintained
Title:     gtk-rs GTK3 bindings - no longer maintained
Date:      2024-03-04
ID:        RUSTSEC-2024-0413
URL:       https://rustsec.org/advisories/RUSTSEC-2024-0413
Dependency tree:
atk 0.18.2
└── gtk 0.18.2
    ├── wry 0.55.0
    │   └── tauri-runtime-wry 2.11.1
    │       └── tauri 2.11.1
    │           ├── tauri-utils 2.9.1
    │           │   ├── tauri-schema-generator 0.0.0
    │           │   ├── tauri-runtime-wry 2.11.1
    │           │   ├── tauri-runtime 2.11.1
    │           │   │   ├── tauri-runtime-wry 2.11.1
    │           │   │   └── tauri 2.11.1
    │           │   ├── tauri-plugin 2.6.1
    │           │   │   ├── tauri-plugin-sample 0.1.0
    │           │   │   │   └── api 0.1.0
    │           │   │   └── tauri-plugin-log 2.6.0
    │           │   │       └── api 0.1.0
    │           │   ├── tauri-macros 2.6.1
    │           │   │   └── tauri 2.11.1
    │           │   ├── tauri-codegen 2.6.1
    │           │   │   ├── tauri-macros 2.6.1
    │           │   │   └── tauri-build 2.6.1
    │           │   │       ├── tauri-file-associations-demo 0.1.0
    │           │   │       ├── tauri 2.11.1
    │           │   │       ├── resources 0.1.0
    │           │   │       ├── bench_helloworld 0.1.0
    │           │   │       ├── bench_files_transfer 0.1.0
    │           │   │       ├── bench_cpu_intensive 0.1.0
    │           │   │       └── api 0.1.0
    │           │   ├── tauri-cli 2.11.1
    │           │   │   └── tauri-cli-node 0.0.0
    │           │   ├── tauri-bundler 2.9.1
    │           │   │   └── tauri-cli 2.11.1
    │           │   ├── tauri-build 2.6.1
</tr></table> 

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps [tauri](https://github.com/tauri-apps/tauri) from 2.11.0 to 2.11.1.
- [Release notes](https://github.com/tauri-apps/tauri/releases)
- [Commits](tauri-apps/tauri@tauri-v2.11.0...tauri-v2.11.1)

---
updated-dependencies:
- dependency-name: tauri
  dependency-version: 2.11.1
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file rust Pull requests that update rust code labels May 7, 2026
@dependabot @github
Copy link
Copy Markdown
Author

dependabot Bot commented on behalf of github May 10, 2026

Looks like tauri is up-to-date now, so this is no longer needed.

@dependabot dependabot Bot closed this May 10, 2026
@dependabot dependabot Bot deleted the dependabot/cargo/src-tauri/tauri-2.11.1 branch May 10, 2026 03:52
t41372 added a commit that referenced this pull request May 19, 2026
…View

Why:
- All seven paper routes now have their primitive components built, but
  each route needs a composition that puts the pieces in the right order
  with the right surrounding cards. Building these three compositions
  (Intelligence, Search, Assistant) in one pass means the actual route
  files just need a small data → composition-props mapping and a route
  mount, like the Browse view's PaperExplorerView pattern.
- Each composition stays presentation-only: the route maps its existing
  data into the typed shape the composition expects, then hands over
  i18n strings and click handlers. This keeps the test surface flat and
  the data layer untouched.

What:
- src/components/explorer-paper/paper-intelligence-view.tsx
  - 4-cell KPI strip → "Topics over the last N days" card with optional
    LLM summary → 2-column grid (top domains + recent sessions left,
    active threads + refind shelf right).
  - Domain / session / thread / refind clicks route to caller handlers.
- src/components/explorer-paper/paper-search-view.tsx
  - PaperSearchHero on top, then one of three branches:
    1. Empty query → PaperSearchEmpty (saved prompts + recent searches).
    2. Empty results → italic-serif "Memory is patient" fallback.
    3. Has results → day-grouped PaperSearchResult rows with the count +
       range header.
  - `belowHeroSlot` lets the route mount provider-gated semantic callouts.
  - Pluralizes singular/plural per the copy template.
- src/components/explorer-paper/paper-assistant-view.tsx
  - Greeting → messages list with auto-scroll on count change → composer
    pinned at the bottom.
  - All handlers (input change, submit, pick prompt, select evidence)
    route straight through.
- Barrel exports added.
- 21 unit tests (6 + 8 + 7) cover: branch selection (greeting / list /
  empty / no-matches / results), selection routing for every handler,
  singular/plural pluralization in Search, evidence routing in Assistant,
  pending state, optional topic summary + axis labels + belowHero slot.

Context: M16 WORK-V03-PAPER-REDESIGN-A task #6 — three of the remaining
five view compositions in place. Next: wire each into its route via the
same `?layout=paper` opt-in pattern Browse uses, then PaperImportView +
PaperAuditView compositions.
t41372 added a commit that referenced this pull request May 19, 2026
Why:
- PaperIntelligenceView has been ready since the view-compositions commit
  but the route didn't yet mount it. With this commit, opening
  `/intelligence?layout=paper` renders the paper KPI strip + domain rank
  list + refind shelf above the existing v0.2 sections, fed by the same
  primary-overview data the route already pulls. The default behaviour
  stays v0.2, so every existing route + section test continues to pass.
- Repeats the Browse view's `?layout=paper` pattern so users can flip
  between the two layouts mid-session and so the route swap stays a
  one-line change once the v0.2 sections retire.

What:
- src/lib/i18n/catalog/explorer.ts: added `explorer.paperIntelligence.*`
  block — 20 keys per locale (en / zh-CN / zh-TW). Catalog now at 2,668
  keys × 3 locales, 100 % parity per `bun run check:i18n`.
- src/pages/explorer/paper-explorer-copy.ts: `buildPaperIntelligenceCopy(t)`
  returns the typed PaperIntelligenceViewCopy bundle. Accepts an optional
  `topicsSummary` override so the route can feed an LLM-supplied summary
  when one is available, otherwise falls back to a deterministic note.
- src/pages/explorer/paper-explorer-copy.test.ts: +5 tests cover the
  builder for English / zh-CN / zh-TW, the LLM summary override path,
  and the missing-key leakage guard.
- src/pages/intelligence/index.tsx: imports + mounts
  `PaperIntelligencePanel` (a small in-file helper) when
  `searchParams.get('layout') === 'paper'`. The panel maps:
  - primaryOverview.topSites → PaperDomainRankRow[]
  - primaryOverview.refindPages → PaperRefindItem[]
  - dashboard.totalVisits + top domain share → 4 KPI cells
  - empty arrays for topics / sessions / threads (those wait on richer
    core-intelligence read models without breaking the layout)
  Domain clicks route through the existing `domainHref()` so deep links
  stay identical to the v0.2 panel.

Context: M16 WORK-V03-PAPER-REDESIGN-A task #6 — Intelligence route is
the second paper route reachable end-to-end (after Browse). Next: same
mount pattern for Search / Assistant / Import / Audit, then backend
annotations and the final `bun run check` sweep.
t41372 added a commit that referenced this pull request May 22, 2026
… i18n

Why
- Codex review flagged three Blocking/High issues against feat/v0.3-redesign-2:
  (1) the ⌘K palette in shell.tsx sent `{ search, limit, offset }` to
      query_history and tried to read `response.rows`, but the real
      contract is `{ q, page, cursor, ... }` returning `items`. Result:
      palette searches were silently empty on desktop, and the existing
      tests had been mocking the wrong shape.
  (2) Paper UI still leaked raw English copy (char/chars counter, "Remove
      tag {tag}" aria, "Calendar" dialog label, "now"/"first" year-rail
      footers, dashboard greetings). i18n is a shipping contract, not
      polish.
  (3) Theme was held twice — once by the shell as a private useState,
      once by Settings → Appearance via applyPaperPreferences. Toggling
      one didn't update the other, so the buttons drifted.

What
- shell.tsx: palette now calls `backend.queryHistory({ q, limit, sort })`
  and maps `response.items` with the real HistoryEntry shape (id/url/
  domain/title/visitedAt/visitTime). Removed the orphan PaletteRow
  interface. shell.test.tsx mocks `backend.queryHistory` with valid
  HistoryQueryResponse fixtures instead of the legacy rows shape.
- i18n: added 3-language entries for the paper detail panel's char
  counter (singular + plural template), the remove-tag aria label, the
  calendar dialog aria, the year-rail now/first footer captions, and
  the dashboard morning/afternoon/evening greetings. The dashboard's
  hand-rolled greeting map is gone — it now reads
  `dashboard.greetingMorning/Afternoon/Evening` like every other copy
  in that route. PaperDetailPanelCopy + PaperCalendarPopoverCopy +
  PaperYearRailProps + paper-view.tsx copy interface all gained the
  new keys; buildPaperDetailPanelCopy + buildPaperContactSheetCopy
  thread them through. i18n parity 100% (2798 keys × 3 locales).
- paper-preferences.ts: applyPaperPreferences now dispatches a
  `pathkeep.paperPreferencesChanged` CustomEvent (with the resolved
  preferences in `detail.preferences`) after applying + persisting.
  shell.tsx subscribes to that event so the topbar theme button stays
  in sync with Settings → Appearance toggles; settings/appearance-
  section.tsx subscribes too so flipping theme via the shell button
  updates the radio without re-mount. shell.tsx's handleToggleTheme
  now routes through applyPaperPreferences instead of mutating a
  private useState — single source of truth, one persist call.

Context
- Codex findings #1, #5, #6. Findings #2 (paper pagination), #3
  (og:image fetch trigger), #4 (coverage gate restoration) tracked
  separately and remain pending in BACKLOG.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
t41372 added a commit that referenced this pull request May 27, 2026
Why
  Claude review finding #6. The S3 cloud backup feature was removed in
  commit 9e0a266 ("S3 cloud backup retired"), which dropped the
  `remoteBackup` field from `AppConfig`. The
  link-previews-section.test.tsx fixture still injected
  `remoteBackup: {} as never,` into its mock snapshot — the `as never`
  cast suppressed the TS mismatch so `bun run check` did not catch it.

  Practical impact today: dead code. Risk: if `AppSnapshot.config`
  ever silently grows a real field shaped like `Record<string, unknown>`,
  the orphan `{}` cast would mask a genuinely missing field on the
  mock. Cosmetic but worth a one-line delete now that we've noticed it.

What
  - Single-line deletion of `remoteBackup: {} as never,` from the
    `mockSnapshot` helper in link-previews-section.test.tsx.
  - All 46 tests in the file still pass; the field's absence matches
    the real `AppConfig` shape.

How
  No type churn anywhere else — this was already orphan data that
  TypeScript could not see through the `never` cast. Removing it just
  realigns the test's view of `AppConfig` with the production view.
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 rust Pull requests that update rust code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants