Commit Graph

9 Commits (d9bb079ec283a8a8b26d2ecbfa9c8ab964817e80)

Author SHA1 Message Date
mula.liu 708bb5b0b1 v 0.1.7 2026-10-26 20:11:20 +08:00
mula.liu 35cca5987c release: 0.1.6 — discover peers across filtered Wi-Fi 2026-10-26 19:53:35 +08:00
mula.liu 579fc6218a release: 0.1.5 — device discovery survives an upgrade
An upgrade emptied the "Send to a device" list, with nothing in the UI to say why.
share.rs was not the cause: the last commit to touch it is b732b91, which only
recorded received files in the history library.

The cause is the macOS Local Network grant. Builds are ad-hoc signed, so every
rebuild is a new code identity, and the grant is keyed to that identity rather than
to the bundle id - 系统设置 now holds five Shift rows, one per build this machine has
run. The declared NSLocalNetworkUsageDescription was missing, so a new identity was
never asked and simply received no group traffic: beacons still went out, direct
unicast was still answered, only the list stayed empty.

That declaration is bc5d3b8. Both READMEs and the packaged macOS note now name the
permission and say what a denial looks like, because unlike Screen Recording it
produces no error - just an empty list. The Developer ID item in M5 records that
this has now actually cost a user a feature, not merely "may reset approvals".

Also ships the Updates panel button pair from 22ff93a, which was merged after 0.1.4
and never published.

Gates: cargo fmt --check clean, cargo test --lib 152 passed / 2 ignored, pnpm check
clean, pnpm test 38 passed. Channel verified by downloading both artifacts back
from the raw endpoint and re-hashing against the manifest, and by the ignored feed
test run with the release key. 55,504,368 B DMG and 24,521,557 B installer.
2026-10-26 19:14:05 +08:00
mula.liu 334082cd9b release: 0.1.4 — figures survive every conversion
Three conversion fixes since 0.1.3, all found with the same two documents:

- DOCX -> PDF kept the text and dropped the pictures, because AppKit's OOXML
  reader returns an attributed string with no attachments at all. An image-bearing
  DOCX now goes through Pandoc into HTML before the same printer, which keeps
  headings, tables and figures. Image-only DOCX files still take the page-scan
  path, and a machine without Pandoc falls back to the old text-only result
  rather than failing.
- Markdown -> DOCX/RTF/HTML lost the same figures for a different reason: a
  Markdown image is a path, Pandoc has to open the file to embed it, and it
  resolves that path against its own working directory, which for a running Shift
  is nowhere near the document. It now gets --resource-path of the source folder.
- A picture that did arrive printed as a cropped fragment. The layout sizes an
  attachment from the density header in the file - 72 dpi when it carries none -
  and ignores CSS, so a 1600 px screenshot asks for 1200 points on a 595 point
  page. The renderer fits oversized attachments to the text column, scaled and
  not resampled. Markdown and HTML documents with wide images are covered too.

The Updates panel's install and discard buttons are one matched pair now, sized to
the panel's own 12px scale instead of the dense 8.5px rows of the Runtime tab they
were borrowed from, and the row drops the discard control while an install is
counting down.

Gates: cargo test --lib 152 passed / 2 ignored, pnpm check clean, pnpm test 38
passed. Artifacts verified from the built bundles, not the build log: the DMG
carries 0.1.4, x86_64 + arm64, Signature=adhoc, and its bundled doc-render places
a wide image at 499pt inside the page; the Windows exe carries the feed URL and
the release public key.
2026-10-26 17:24:22 +08:00
mula.liu c98d554a88 release: 0.1.3 — the Recent list survives an upgrade
The Updates tab drops the "installs the ... artifact" chip, and the state label
now leads the status row instead of floating right, since the version it used to
sit beside moved into the header.

The file list no longer disappears on upgrade:

- The library already lived in the app data directory, outside the bundle, so an
  in-app update or reinstall never touched `history.json`. What it never had was a
  bridge from the store 0.1 used: that list lived in the webview's own storage,
  which a reinstall does not survive, so the first launch of a newer build showed
  an empty Recent list over files that were all still on disk.
- `history_import` merges those rows once, on the first launch after an upgrade.
  An entry the library already lists keeps its own timestamp, the kind is
  re-derived from the file rather than taken from the older store's guess, and the
  legacy key is dropped only after the merge succeeds so a later upgrade cannot
  resurrect rows the user has since removed.
- `HistoryEntry.kind`/`.at` gained serde defaults, so a row from the older store
  degrades to a usable entry instead of failing the whole import.

Verified on this machine that the legacy `shift.recent` key is still present in the
installed app's webview store, so the import has rows to adopt.

Gates: cargo fmt --check clean, `cargo test --lib` 149 passed / 2 ignored,
`pnpm check` clean, `pnpm test` 38 passed, `pnpm build` ok.
2026-10-26 04:02:31 +08:00
mula.liu 15498482fa release: 0.1.2 — install the update in place, and lead the tab with the host
Updates now finish without leaving the app. After the SHA256 gate, macOS replaces
its own `.app` from the downloaded disk image and Windows runs the same NSIS
installer with `/S`; both from a detached helper that waits for this process to
exit and then opens the new copy.

- `update.rs`: `bundle_path` (is this a bundled run?), `can_replace` (is the
  enclosing folder writable — checked before quitting, not after), and the two
  handoff scripts. Every macOS failure path still `open`s the bundle it had, so a
  failed swap leaves Shift running rather than closed.
- `windows-installer.nsi`: `${Silent}` skips the "Shift is running, close it?"
  box, which would otherwise abort an update nobody is there to answer.
- `useUpdate.ts`: a failed install reports its own error and keeps the verified
  download, instead of downgrading a "ready" status to "error".

The Updates tab now leads with two lines above everything else: system,
architecture and running version, then the feed URL. The header no longer repeats
the version in the status row.

Verified end to end on macOS: a 0.1.1 bundle swapped by the published 0.1.2 image,
`codesign --verify --deep --strict` clean afterwards, image detached, and the
busy-image path shown to reopen the old copy.

Gates: cargo fmt --check clean, `cargo test --lib` 146 passed / 2 ignored,
`pnpm check` clean, `pnpm test` 34 passed, `pnpm build` ok.
2026-10-26 03:41:47 +08:00
mula.liu b732b91ea6 release: 0.1.1 — update channel, settings/UI trims, macOS + Windows x64 only
Update path
- `src-tauri/src/update.rs`: manifest fetch, semver compare, optional ed25519
  signature check against a key baked in at build time, then a size + SHA256
  gate before an installer can run. `UpdateStatus` now reports the artifact key
  it resolved so the UI can name what it will install.
- Settings → Updates panel shows the feed, the check/download state machine, and
  the local OS, architecture and release artifact for this machine.
- `scripts/publish-release.sh` + `scripts/release-key.py` publish installers and a
  signed `shift-update.json` onto an orphan `releases` branch.

Scope trims requested for this release
- Settings: the Radial rings tab is gone, so ring orders are read from
  `settings.json` with no in-app editor for now.
- Main window: the update entry in the header bar is gone; updates live in
  Settings → Updates only.
- Release targets are macOS universal and Windows x64. ARM64 and Linux stay
  buildable and are no longer published; `docs/RELEASE.md` records the decision.

Gates: cargo fmt --check clean, `cargo test --lib` 142 passed / 2 ignored,
`pnpm check` clean, `pnpm test` 34 passed, `pnpm build` ok.
2026-10-26 03:06:46 +08:00
mula.liu c6eff4e131 修复bug 2026-10-25 12:24:05 +08:00
Shift 0eb75595c6 baseline: capture workspace state (bug fixes in progress) 2026-10-21 08:54:54 +08:00