fix: 更新下载页面到最新 release 链接#19
Conversation
Reviewer's Guide更新文档以引用 v1.0.1 版本,包括将展示用版本号与下载 URL 中资源命名所用的版本号分离,并在三种语言的文档中添加 v1.0.1 的更新日志条目。 版本配置和下载页面的类图classDiagram
class VersionConfig {
+string VERSION
+string RELEASE_TAG
+string RELEASE_BASE
+string ASSET_VERSION
+string ARCH_PKG_ASSET_VERSION
}
class EnDownloadPage {
+renderWindowsLinks()
+renderMacOSLinks()
+renderLinuxLinks()
}
class ZhDownloadPage {
+renderWindowsLinks()
+renderMacOSLinks()
+renderLinuxLinks()
}
class ZhTwDownloadPage {
+renderWindowsLinks()
+renderMacOSLinks()
+renderLinuxLinks()
}
VersionConfig <.. EnDownloadPage : uses
VersionConfig <.. ZhDownloadPage : uses
VersionConfig <.. ZhTwDownloadPage : uses
构建发布资源下载 URL 的流程图flowchart LR
VERSION[VERSION 1.0.1]
RELEASE_TAG[v1.0.1]
ASSET_VERSION[ASSET_VERSION 1.0.0-1]
ARCH_PKG_ASSET_VERSION[ARCH_PKG_ASSET_VERSION 1.0.1-1]
RELEASE_TAG --> RELEASE_BASE[RELEASE_BASE https://github.com/SeaLantern-Studio/SeaLantern/releases/download/RELEASE_TAG]
subgraph Windows_and_macOS_assets
ASSET_VERSION --> Win_exe[Sea.Lantern_ASSET_VERSION_x64-setup.exe]
ASSET_VERSION --> Win_msi[Sea.Lantern_ASSET_VERSION_x64_zh-CN.msi]
ASSET_VERSION --> Win_exe_arm64[Sea.Lantern_ASSET_VERSION_arm64-setup.exe]
ASSET_VERSION --> Win_msi_arm64[Sea.Lantern_ASSET_VERSION_arm64_zh-CN.msi]
ASSET_VERSION --> Mac_aarch64_dmg[Sea.Lantern_ASSET_VERSION_aarch64.dmg]
ASSET_VERSION --> Mac_x64_dmg[Sea.Lantern_ASSET_VERSION_x64.dmg]
end
subgraph Linux_assets
ASSET_VERSION --> Deb_amd64[Sea.Lantern_ASSET_VERSION_amd64.deb]
ASSET_VERSION --> Deb_arm64[Sea.Lantern_ASSET_VERSION_arm64.deb]
ASSET_VERSION --> Rpm_x86_64[Sea.Lantern-ASSET_VERSION.x86_64.rpm]
ASSET_VERSION --> Rpm_aarch64[Sea.Lantern-ASSET_VERSION.aarch64.rpm]
ASSET_VERSION --> AppImage_amd64[Sea.Lantern_ASSET_VERSION_amd64.AppImage]
ASSET_VERSION --> AppImage_aarch64[Sea.Lantern_ASSET_VERSION_aarch64.AppImage]
ARCH_PKG_ASSET_VERSION --> Arch_pkg[sealantern-ARCH_PKG_ASSET_VERSION-x86_64.pkg.tar.zst]
end
RELEASE_BASE --> Win_exe
RELEASE_BASE --> Win_msi
RELEASE_BASE --> Win_exe_arm64
RELEASE_BASE --> Win_msi_arm64
RELEASE_BASE --> Mac_aarch64_dmg
RELEASE_BASE --> Mac_x64_dmg
RELEASE_BASE --> Deb_amd64
RELEASE_BASE --> Deb_arm64
RELEASE_BASE --> Rpm_x86_64
RELEASE_BASE --> Rpm_aarch64
RELEASE_BASE --> AppImage_amd64
RELEASE_BASE --> AppImage_aarch64
RELEASE_BASE --> Arch_pkg
文件级变更
提示和命令与 Sourcery 交互
自定义你的体验访问你的 仪表盘 以:
获取帮助Original review guide in EnglishReviewer's GuideUpdates docs to reference the v1.0.1 release, including separating display version from asset naming for download URLs and adding v1.0.1 changelog entries in all three languages. Class diagram for version configuration and download pagesclassDiagram
class VersionConfig {
+string VERSION
+string RELEASE_TAG
+string RELEASE_BASE
+string ASSET_VERSION
+string ARCH_PKG_ASSET_VERSION
}
class EnDownloadPage {
+renderWindowsLinks()
+renderMacOSLinks()
+renderLinuxLinks()
}
class ZhDownloadPage {
+renderWindowsLinks()
+renderMacOSLinks()
+renderLinuxLinks()
}
class ZhTwDownloadPage {
+renderWindowsLinks()
+renderMacOSLinks()
+renderLinuxLinks()
}
VersionConfig <.. EnDownloadPage : uses
VersionConfig <.. ZhDownloadPage : uses
VersionConfig <.. ZhTwDownloadPage : uses
Flow diagram for constructing release asset download URLsflowchart LR
VERSION[VERSION 1.0.1]
RELEASE_TAG[v1.0.1]
ASSET_VERSION[ASSET_VERSION 1.0.0-1]
ARCH_PKG_ASSET_VERSION[ARCH_PKG_ASSET_VERSION 1.0.1-1]
RELEASE_TAG --> RELEASE_BASE[RELEASE_BASE https://github.com/SeaLantern-Studio/SeaLantern/releases/download/RELEASE_TAG]
subgraph Windows_and_macOS_assets
ASSET_VERSION --> Win_exe[Sea.Lantern_ASSET_VERSION_x64-setup.exe]
ASSET_VERSION --> Win_msi[Sea.Lantern_ASSET_VERSION_x64_zh-CN.msi]
ASSET_VERSION --> Win_exe_arm64[Sea.Lantern_ASSET_VERSION_arm64-setup.exe]
ASSET_VERSION --> Win_msi_arm64[Sea.Lantern_ASSET_VERSION_arm64_zh-CN.msi]
ASSET_VERSION --> Mac_aarch64_dmg[Sea.Lantern_ASSET_VERSION_aarch64.dmg]
ASSET_VERSION --> Mac_x64_dmg[Sea.Lantern_ASSET_VERSION_x64.dmg]
end
subgraph Linux_assets
ASSET_VERSION --> Deb_amd64[Sea.Lantern_ASSET_VERSION_amd64.deb]
ASSET_VERSION --> Deb_arm64[Sea.Lantern_ASSET_VERSION_arm64.deb]
ASSET_VERSION --> Rpm_x86_64[Sea.Lantern-ASSET_VERSION.x86_64.rpm]
ASSET_VERSION --> Rpm_aarch64[Sea.Lantern-ASSET_VERSION.aarch64.rpm]
ASSET_VERSION --> AppImage_amd64[Sea.Lantern_ASSET_VERSION_amd64.AppImage]
ASSET_VERSION --> AppImage_aarch64[Sea.Lantern_ASSET_VERSION_aarch64.AppImage]
ARCH_PKG_ASSET_VERSION --> Arch_pkg[sealantern-ARCH_PKG_ASSET_VERSION-x86_64.pkg.tar.zst]
end
RELEASE_BASE --> Win_exe
RELEASE_BASE --> Win_msi
RELEASE_BASE --> Win_exe_arm64
RELEASE_BASE --> Win_msi_arm64
RELEASE_BASE --> Mac_aarch64_dmg
RELEASE_BASE --> Mac_x64_dmg
RELEASE_BASE --> Deb_amd64
RELEASE_BASE --> Deb_arm64
RELEASE_BASE --> Rpm_x86_64
RELEASE_BASE --> Rpm_aarch64
RELEASE_BASE --> AppImage_amd64
RELEASE_BASE --> AppImage_aarch64
RELEASE_BASE --> Arch_pkg
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
There was a problem hiding this comment.
Hey,我这边发现了两个问题,并且有一些整体性的反馈:
- 既然 VERSION、ASSET_VERSION 和 ARCH_PKG_ASSET_VERSION 现在可能不再保持一致,建议将它们集中到一个带类型的配置对象中(例如按平台区分的 metadata),或者增加一个用于生成资源 URL 的小工具函数,这样以后版本升级时就不需要手动维护三份常量并保持同步了。
给 AI Agent 的提示
请根据本次代码评审中的评论进行修改:
## 整体反馈
- 既然 VERSION、ASSET_VERSION 和 ARCH_PKG_ASSET_VERSION 现在可能不再保持一致,建议将它们集中到一个带类型的配置对象中(例如按平台区分的 metadata),或者增加一个用于生成资源 URL 的小工具函数,这样以后版本升级时就不需要手动维护三份常量并保持同步了。
## 单条评论
### Comment 1
<location path="en/changelog.md" line_range="14" />
<code_context>
+### Fixes & Improvements
+- Replaced installer links
+- Added commit conventions and formatting hooks
+- Optimized terminal log system with xtermjs and sqlite
+
+---
</code_context>
<issue_to_address>
**suggestion (typo):** 建议使用 xterm.js 和 SQLite 的官方大小写形式。
具体来说,将本条 bullet 中的 `xtermjs` → `xterm.js`,`sqlite` → `SQLite`。
Suggested implementation:
```
- Optimized terminal log system with xterm.js and SQLite
```
只要在 `en/changelog.md` 中存在这条完全相同的 bullet 行,就不需要做其他代码改动。如果该行的文案略有不同(例如在 `xtermjs` 或 `sqlite` 前后有额外文本),请在应用替换前先调整搜索行,使其与实际内容完全一致。
</issue_to_address>
### Comment 2
<location path="zh-tw/changelog.md" line_range="14" />
<code_context>
+### 修復與優化
+- 更換安裝器連結
+- 新增提交規範與格式化 hooks
+- 使用 xtermjs 與 sqlite 優化終端日誌系統
+
+---
</code_context>
<issue_to_address>
**suggestion (typo):** 建議將 xtermjs 與 sqlite 改為官方命名形式。
例如改為 `xterm.js` 與 `SQLite`,以符合官方寫法。
Suggested implementation:
```
- 新增提交規範與格式化 hooks
- 使用 xterm.js 與 SQLite 優化終端日誌系統
```
```
### 修復與優化
- 使用 xterm.js 與 SQLite 優化終端日誌系統
```
</issue_to_address>请帮我变得更有用!可以对每条评论点 👍 或 👎,我会根据你的反馈改进后续评审质量。
Original comment in English
Hey - I've found 2 issues, and left some high level feedback:
- Now that VERSION, ASSET_VERSION, and ARCH_PKG_ASSET_VERSION can diverge, consider centralizing them in a single typed config object (e.g., per-platform metadata) or adding a small helper to generate asset URLs so future bumps don’t require manually keeping three separate constants in sync.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- Now that VERSION, ASSET_VERSION, and ARCH_PKG_ASSET_VERSION can diverge, consider centralizing them in a single typed config object (e.g., per-platform metadata) or adding a small helper to generate asset URLs so future bumps don’t require manually keeping three separate constants in sync.
## Individual Comments
### Comment 1
<location path="en/changelog.md" line_range="14" />
<code_context>
+### Fixes & Improvements
+- Replaced installer links
+- Added commit conventions and formatting hooks
+- Optimized terminal log system with xtermjs and sqlite
+
+---
</code_context>
<issue_to_address>
**suggestion (typo):** Consider using the official capitalization for xterm.js and SQLite.
Specifically, update `xtermjs` → `xterm.js` and `sqlite` → `SQLite` in this bullet point.
Suggested implementation:
```
- Optimized terminal log system with xterm.js and SQLite
```
No further code changes are required as long as this exact bullet line exists somewhere in `en/changelog.md`. If the line’s wording differs slightly (e.g., extra text around `xtermjs` or `sqlite`), adjust the SEARCH line to match the actual content exactly before applying this replacement.
</issue_to_address>
### Comment 2
<location path="zh-tw/changelog.md" line_range="14" />
<code_context>
+### 修復與優化
+- 更換安裝器連結
+- 新增提交規範與格式化 hooks
+- 使用 xtermjs 與 sqlite 優化終端日誌系統
+
+---
</code_context>
<issue_to_address>
**suggestion (typo):** 建議將 xtermjs 與 sqlite 改為官方命名形式。
例如改為 `xterm.js` 與 `SQLite`,以符合官方寫法。
Suggested implementation:
```
- 新增提交規範與格式化 hooks
- 使用 xterm.js 與 SQLite 優化終端日誌系統
```
```
### 修復與優化
- 使用 xterm.js 與 SQLite 優化終端日誌系統
```
</issue_to_address>Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
| ### Fixes & Improvements | ||
| - Replaced installer links | ||
| - Added commit conventions and formatting hooks | ||
| - Optimized terminal log system with xtermjs and sqlite |
There was a problem hiding this comment.
suggestion (typo): 建议使用 xterm.js 和 SQLite 的官方大小写形式。
具体来说,将本条 bullet 中的 xtermjs → xterm.js,sqlite → SQLite。
Suggested implementation:
- Optimized terminal log system with xterm.js and SQLite
只要在 en/changelog.md 中存在这条完全相同的 bullet 行,就不需要做其他代码改动。如果该行的文案略有不同(例如在 xtermjs 或 sqlite 前后有额外文本),请在应用替换前先调整搜索行,使其与实际内容完全一致。
Original comment in English
suggestion (typo): Consider using the official capitalization for xterm.js and SQLite.
Specifically, update xtermjs → xterm.js and sqlite → SQLite in this bullet point.
Suggested implementation:
- Optimized terminal log system with xterm.js and SQLite
No further code changes are required as long as this exact bullet line exists somewhere in en/changelog.md. If the line’s wording differs slightly (e.g., extra text around xtermjs or sqlite), adjust the SEARCH line to match the actual content exactly before applying this replacement.
| ### 修復與優化 | ||
| - 更換安裝器連結 | ||
| - 新增提交規範與格式化 hooks | ||
| - 使用 xtermjs 與 sqlite 優化終端日誌系統 |
There was a problem hiding this comment.
suggestion (typo): 建議將 xtermjs 與 sqlite 改為官方命名形式。
例如改為 xterm.js 與 SQLite,以符合官方寫法。
Suggested implementation:
- 新增提交規範與格式化 hooks
- 使用 xterm.js 與 SQLite 優化終端日誌系統
### 修復與優化
- 使用 xterm.js 與 SQLite 優化終端日誌系統
Original comment in English
suggestion (typo): 建議將 xtermjs 與 sqlite 改為官方命名形式。
例如改為 xterm.js 與 SQLite,以符合官方寫法。
Suggested implementation:
- 新增提交規範與格式化 hooks
- 使用 xterm.js 與 SQLite 優化終端日誌系統
### 修復與優化
- 使用 xterm.js 與 SQLite 優化終端日誌系統
There was a problem hiding this comment.
Pull request overview
This PR updates the VitePress docs to reflect the latest SeaLantern release (v1.0.1), including changelog entries and download links that match the current release asset naming across CN / TW / EN pages.
Changes:
- Bumped docs “latest version” constants to
v1.0.1and introduced per-platform asset version constants in.vitepress/version.ts. - Updated download links in
zh/,zh-tw/, anden/download pages to use the new asset version constants. - Added
v1.0.1sections to CN / TW / EN changelogs and moved the “Latest/最新” badge to the new version.
Reviewed changes
Copilot reviewed 7 out of 7 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
.vitepress/version.ts |
Bumps version/tag and adds asset-version constants used to build download URLs. |
zh/download.md |
Switches Windows/macOS/Linux download URLs to the updated asset naming variables. |
zh/changelog.md |
Adds v1.0.1 entry and updates the “最新” marker. |
zh-tw/download.md |
Switches download URLs to the updated asset naming variables. |
zh-tw/changelog.md |
Adds v1.0.1 entry and updates the “最新” marker. |
en/download.md |
Switches download URLs to the updated asset naming variables. |
en/changelog.md |
Adds v1.0.1 entry and updates the “Latest” marker. |
Comments suppressed due to low confidence (3)
en/changelog.md:15
- 更新日志里第三条提到的依赖名称建议使用官方写法以避免歧义:
xtermjs通常写作xterm.js,sqlite通常写作SQLite。
### Fixes & Improvements
- Replaced installer links
- Added commit conventions and formatting hooks
- Optimized terminal log system with xtermjs and sqlite
zh/changelog.md:15
- 更新日志里第三条提到的依赖名称建议使用官方写法以避免歧义:
xtermjs通常写作xterm.js,sqlite通常写作SQLite。
### 修复与优化
- 更换安装器链接
- 增加提交规范与格式化钩子
- 使用 xtermjs 与 sqlite 优化终端日志系统
zh-tw/changelog.md:15
- 更新日誌第三點提到的依賴名稱建議使用官方寫法以避免歧義:
xtermjs通常寫作xterm.js,sqlite通常寫作SQLite。
### 修復與優化
- 更換安裝器連結
- 新增提交規範與格式化 hooks
- 使用 xtermjs 與 sqlite 優化終端日誌系統
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| /** 当前最新版本号,更新时只需修改此处 */ | ||
| export const VERSION = '1.0.0' | ||
| export const VERSION = '1.0.1' | ||
|
|
||
| /** GitHub Release 的 tag(不同版本可能不是固定命名规则) */ | ||
| export const RELEASE_TAG = 'v1.0.0' | ||
| export const RELEASE_TAG = 'v1.0.1' | ||
|
|
||
| /** GitHub Release 下载基础 URL */ | ||
| export const RELEASE_BASE = `https://github.com/SeaLantern-Studio/SeaLantern/releases/download/${RELEASE_TAG}` | ||
|
|
||
| /** 安装包资产版本(受上游打包命名影响,可能与 VERSION 不一致) */ | ||
| export const ASSET_VERSION = '1.0.0-1' | ||
|
|
||
| /** Arch 包资产版本(当前发布命名与其它平台不同) */ | ||
| export const ARCH_PKG_ASSET_VERSION = '1.0.1-1' |
There was a problem hiding this comment.
version.ts 现在需要同时维护 VERSION、RELEASE_TAG、ASSET_VERSION、ARCH_PKG_ASSET_VERSION,但文件头注释仍写“更新时只需修改此处”,容易误导并导致漏改(尤其当 ASSET_VERSION 与 VERSION 不一致时)。建议更新注释说明需要同步更新哪些常量,或让 RELEASE_TAG/asset 版本默认从 VERSION 派生(仅在确有差异时覆写)。
变更内容
验证
Summary by Sourcery
更新站点版本元数据和文档,使其引用 v1.0.1 版本及其相关资源。
Bug Fixes:
Enhancements:
Original summary in English
Summary by Sourcery
Update site version metadata and docs to reference the v1.0.1 release and its assets.
Bug Fixes:
Enhancements: