Skip to content

docs(manual): sync published v1.5.0 - #249

Merged
singkia merged 1 commit into
mainfrom
docs/release-v1.5.0
Oct 19, 2026
Merged

singkia merged 1 commit into
mainfrom
docs/release-v1.5.0

Conversation

@singkia

@singkia singkia commented Oct 19, 2026

Copy link
Copy Markdown
Contributor

Summary

Synchronize the manual with the published v1.5.0 release:

  • Copy the approved, published English and Chinese release-note blocks verbatim; record the actual publication time and tag commit.
  • Advance the documented stable baseline, language landing pages and release indexes to v1.5.0.
  • Align permission setup, perm, Runtime, update and troubleshooting guides with registered default macOS recovery and the explicit legacy signing migration.
  • Preserve historical release pages and the macOS 26, cross-signing and experimental Windows limits. No product, dependency, lockfile or workflow changes.

Verification

  • Complete manual check passes: 58 built HTML pages and 5,319 local links/assets plus agent/search endpoints checked.
  • Security audit passes with zero findings; 58 files lint clean.
  • Both language blocks exactly match the canonical GitHub Release body. Stable version, publication timestamp and source commit match the real Release.
  • Initial local build missed an optional Pagefind binary after a failed dependency fetch. Reinstalling the exact lockfile with optional dependencies restored Pagefind; no package/configuration change or search/link-check bypass was used.
  • Independent read-only content review found no blocking issues. CI remains required before merge.

逐字复制已批准并公开的双语发布说明,更新真实发布时间、tag来源和稳定基线。对齐双权限与默认macOS恢复的现有行为,保留跨签名、macOS26及Windows实验边界;不改历史版本。
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 19, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-19T12:48:52.706929Z c7f3188 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@singkia
singkia merged commit 123e7d9 into main Oct 19, 2026
6 checks passed

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c7f3188c5b

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

## Upgrade from v1.4.0

For Homebrew, script or managed Windows installations, run `inc update` first. For a source installation, update your checkout with `git pull`, then run `cargo install --locked --path crates/incodex-cli` and `incodex runtime`. If you already use app integration, finish active work, exit Codex normally, and run `incodex install` once to refresh the macOS loader catalog or Windows helper. On macOS, repeat your original `--app <path>` or `--clone` option if you used one. If you only use `incodex open`, update and reopen your private window; no installation is needed. After setup, compatible UI/action changes apply to supported running windows; other Runtime changes require reopening and native/helper/loader changes require installation. Already-open incognito windows retain their privacy Runtime until normal close.
For Homebrew, script or managed Windows installations, run `inc update`. For a source installation, update your checkout with `git pull`, then run `cargo install --locked --path crates/incodex-cli` and `incodex runtime`.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Preserve the skipped-v1.4 helper migration

For Windows users upgrading directly from v1.3.x, or who never completed v1.4's one-time setup, this now instructs them to run only inc update and removes the explicit normal-exit incodex install step. README.md:109 still requires that install to refresh the Windows helper, and Runtime publication cannot upgrade an older native helper, so these users remain on a helper that cannot enable the installed hot-update controller. Retain the v1.4 migration note or explicitly require pre-v1.4 integrations to reinstall.

AGENTS.md reference: AGENTS.md:L129-L132

Useful? React with 👍 / 👎.

@singkia

singkia commented Oct 19, 2026

Copy link
Copy Markdown
Contributor Author

v1.5.0 delivery verified

Follow-through for #245, #247 and this documentation sync:

  • v1.5.0 is published from 0e105404820bb76b3333ae1542321ab7cee77964, with the approved bilingual notes and all four expected assets. Downloads match both SHA256SUMS and the API digests. The native release pipeline and tap update passed.
  • This manual sync merged as 123e7d9a6a3a4c8d7a366cd68b61994ef478f7bf; its exact Pages deployment passed.
  • The live English and Chinese release pages and their Markdown endpoints were read back. Both language blocks match the canonical Release; the live Pagefind asset is present.
  • Product implementation and bundled Runtime assets did not change in this documentation follow-up. Existing Windows experiment and macOS acceptance limits remain explicit.

@singkia
singkia deleted the docs/release-v1.5.0 branch October 19, 2026 17:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant