Repository navigation
fix(app): clarify site entry and update guidance - #458
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem and outcome / 问题与结果
The App's update notice lacked a separate release-note link and any distinction
for a new major release. Site entry also required users to supply the URL scheme.
This maintenance phase keeps direct manual downloads, adds concise major-upgrade
guidance in the App and Server log, and accepts bare Site domains through the
existing App normalizer. Explicit HTTP/HTTPS origins retain their meaning.
The shared launcher preview and accessibility copy follow the same behavior.
Website brand baselines are aligned; source-map-js is updated to 1.2.2 in both
build lockfiles. Windows capture self-tests now retain the first worker exception
and report the failing phase and output progress without changing deadlines or
production capture behavior. The Magicsock assessment remains documentation only.
Release notes
中文
这是一次维护更新,重点改善 Piik App 的站点连接和版本更新体验。现有设置和连接协议保持兼容。
English
This maintenance update makes Piik App's Site entry and update notices easier to use. Existing settings and connection protocols remain compatible.
Verification / 验证
npm run check: 81 test files / 1,378 tests passed; type checking and production Web build passed.npm run build:website: homepage, film and bilingual documentation build passed.exact package/release links, no download during detection, missing-package page
fallback, Chinese/English/visual modes, light/dark themes, 320–1440px layouts and
scoped accessibility checks passed. Network metadata is simulated in these checks.
App configuration and launcher tests passed, including normalization and invalid
origins. Go vet passed for the affected packages.
and Web bundle-size warnings remain.
npm run check:go: Go tests, formatting, vet, registered non-Darwin targetbuilds, Windows native build, deterministic capture regressions, probe and source
enumeration passed. Darwin cgo builds were skipped on this Windows runner as designed.
Impact / 影响
Maintenance release: v1.9.2. No public wire or storage change: Browser/server v23,
Native control v9, capture v7 and SQLite schema 2 are unchanged. No media, route,
room-authority or automatic-installation behavior changes. Site origin validation
remains strict; a missing scheme defaults to HTTPS without network probing or
silent HTTP fallback. Configs written by this version still contain complete origins.
Historical installed Apps retain their released update behavior. Future major
upgrades still need release-specific compatibility instructions. Physical macOS/Linux
capture and reporter-dependent issues remain outside this maintenance change.