mirror of
https://github.com/getpaseo/paseo.git
synced 2026-10-28 12:12:47 +00:00
Mohamed Boudra
bd15e40e94
* feat(website): serve paseo.sh in Simplified Chinese
Every page of the website now has a Simplified Chinese version under
/zh-CN: the interface, docs, blog posts, comparison pages, legal pages,
all changelog releases and the homepage mockup. English URLs are unchanged.
The URL alone decides the language. There is no browser-language redirect
and no stored preference, because either would have to redirect the
unprefixed English URLs that people share and search engines index.
Internal links carry the page's language instead, and hreflang alternates
point Chinese search results at /zh-CN.
Translated headings pin the English anchor with {#id}, so section links
work in both languages. content-translations.test.ts fails when a page
has no translation or a translation's headings drift from the English.
Changelog releases and plugin listings without a translation render
whole in English under a notice, so a release never waits on one.
Plugin manifests and the registry gain optional translations and
OVERVIEW.zh-CN.md fields; older clients and registries ignore them.
* feat(website): replace the native language select with an EN/ZH menu
The header showed an OS-native select whose popup did not match the site.
The trigger now shows the language abbreviated (EN, ZH) and opens a menu in
the app's dropdown style that names each language in itself, with its name
in the page language underneath. Rows are real links to the same page in
that language; arrows, Escape, outside presses and taps behave as a menu
button, and the menu keeps itself on screen when a narrow header pushes the
trigger toward an edge.
Also drops the stray space after the full-width comma in the Chinese
homepage subtitle.
* docs(website): translate main's new docs and 0.12.0 release notes
Main added Keep run workspaces to the schedules docs, rewrote plugin icons
around inline SVG, and promoted 0.12.0 with new entries. Bring the Chinese
pages and changelog in line so no section falls back to English.
* fix(server): leave plugin listing translations to the registry
The daemon rejected manifests whose translations the registry would refuse,
so a plugin main installs could fail to load here. Paseo never reads
translations; the registry validates them at publish. Docs now say which
checks are automated at publish and which are human review.
* docs(plugins): describe the registry's final overview translation discovery
* style(server): format manifest test
* test(app): measure sidebar rows one at a time
After a reload the developer error toast appears while expectVerticalOrder
measures every row at once. Each concurrent boundingBox runs the toast
locator handler, and only one of them resumes, so the poll timed out on
every attempt since #7424. Measuring sequentially keeps one action in flight.
* test(app): return sidebar row measuring to main
#7480 hides the developer toast instead of running a locator handler, so
measuring the rows concurrently no longer races it. Reverts 41ac23016.
* test(app): wait for the compact shell before opening compact Changes
The shell survives the breakpoint, so right after the resize the wide
Explorer could still be visible: the test skipped the Explorer toggle and
the tab then disappeared, or toggled at the wrong time. Wait for the
compact-shell marker, as the composer helpers do since #7424.
* docs(website): translate main's plugin file panel docs
* test(app): edit the code font size after the font family remount
A committed appearance change remounts the settings screen through
AppearanceStyleBoundary, and the new form starts from the stored size.
Filling the size before that remount lost the edit in CI.
* docs(website): translate main's client/ui import docs
Follows #7474: one /client/ui entry, StreamedText instead of useRevealedText,
SettingsGroup dropped from the settings table, and the new
'UI imports in v0.13' migration section.
* test(app): wait for the previous layout's file panel picker to leave
After a resize the old layout's picker animates out while the new one is
already mounted, so the Use button matched two elements and the strict
locator failed. Wait for the shell's layout and a single picker first.
2.6 KiB
2.6 KiB
title, description, nav
| title | description | nav |
|---|---|---|
| 更新 | Paseo 如何发布版本、稳定版与测试版渠道的区别，以及如何提前获取更新。 | 更新 |
更新
Paseo 通过两个渠道发布更新：Stable（稳定版）和 Beta（测试版）。
大多数版本在稳定版渠道发布。测试版是候选版本，让你在新内容推送给所有人之前先行测试。
版本号
Paseo 遵循带预发布标签的语义化版本。
稳定版看起来是这样：
v0.1.90
同一版本的测试版看起来是这样：
v0.1.90-beta.1
如果某个版本需要更多测试，我们会发布更多测试版：
v0.1.92-beta.1
v0.1.92-beta.2
v0.1.92-beta.3
版本准备就绪后，最终的稳定版标签是 v0.1.92，而不是 v0.1.93。这些测试版是通往同一个稳定版本的检查点。
稳定版渠道
稳定版渠道是默认渠道。桌面端稳定版会在 36 小时内逐步推送，这样即使有意外问题漏网，也不会同时影响所有人。自动更新检查会随着推送进度获取新版本；在应用中点击 检查 会跳过分批推送，立即安装。
大多数用户应该使用稳定版。
测试版渠道
测试版渠道在每个预发布版本发布后立即收到它，没有推送延迟。当某个测试版升级为稳定版时，测试版用户也会立即收到这个稳定版更新。
测试版是提前获得修复和新功能的最佳方式。如果遇到 bug，请报告；测试版的反馈让稳定版更加可靠。
如何加入测试版渠道
在桌面应用中：
- 打开 设置
- 进入 关于
- 在 发布通道 下选择 Beta
之后应用就会检查测试版更新。
应用商店
桌面端版本和 CLI 通常最先提供。App Store 和 Play Store 的版本需要经过审核，可能会滞后。
应用商店目前没有测试版渠道，只提交稳定版构建。如果你想提前使用 Android 构建，请从 GitHub releases 页面下载 APK。
出现问题怎么办
测试版难免有不完善之处。如果某个测试版带来问题，你可以在 设置 → 关于 → 发布通道 中切换回稳定版渠道。下一个稳定版更新会正常安装。
如果你需要一个尚未发布到稳定版的修复，请留在测试版并报告问题。测试版中发现的大多数问题都会在稳定版发布前修复。