Commit Graph

7 Commits (d9bb079ec283a8a8b26d2ecbfa9c8ab964817e80)

Author SHA1 Message Date
mula.liu d9bb079ec2 docs: record discovery, conversion and macOS packaging regressions 2026-10-26 20:24:21 +08:00
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 58949bebd2 docs: macOS ships the DMG alone, the pkg is retired
The .pkg existed to hand a fresh machine a copy that was not quarantined, so it
opened with no prompt at all. The DMG has now been verified to work on a fresh
machine - drag to /Applications, one approval on first launch - which is the same
one approval the DMG has always needed. So the second container bought nothing
and is dropped: one artifact per platform is less to keep straight, and nothing in
the channel changes.

What the docs say instead of recommending the package: install the DMG, allow the
first launch once. In-app updates still never prompt, because Shift's own
downloader sets no quarantine flag. The macos manifest key stays a DMG for the
reason it always did - the in-app handoff mounts it with hdiutil.

scripts/macos-pkg.sh stays in the tree and RELEASE.md says plainly that it is no
longer part of a release, so the next reader does not wonder whether a publish is
missing it. The 0.1.3 branch still holds the retired package because removing it
means re-publishing; it has no manifest key, so nothing can be served it.

The packaged note is rewritten for the same reason: it told a reader to download a
file that will no longer be built, and its verification section checked the
package instead of the image.
2026-10-26 10:47:48 +08:00
mula.liu f2a1ff6d52 docs: record the macOS packaging scheme next to the artifacts
The ad-hoc signature, the two containers and their different jobs, and how to
verify a download were explained only in docs/RELEASE.md. A user who downloads
Shift-macOS-universal.pkg from the releases branch never sees that file, so the
same write-up now also ships as artifacts/README-macOS-universal.txt, beside the
per-arch Windows notes that already travelled with the channel.

Every claim was checked against the shipped artifacts rather than carried over:
the .pkg payload is Signature=adhoc, pkgutil --check-signature reports no
signature for the package itself, and shasum -c passes on the published set. The
file is force-added to the repository even though artifacts/ is gitignored, so
the scheme is documented where a contributor reads it.
2026-10-26 10:40:33 +08:00