Skip to content

release: OpenLess 2.0.2-Beta.5 desktop refresh and usage improvements - #1423

Merged
appergb merged 59 commits into
betafrom
release/2.0.2-beta.5
Nov 9, 2026
Merged

appergb merged 59 commits into
betafrom
release/2.0.2-beta.5

Conversation

@appergb

@appergb appergb commented Nov 9, 2026 •

Copy link
Copy Markdown
Collaborator

Prepare 2.0.2-Beta.5+build.20261109-47405c88 from the accepted desktop preview. This integrates the settings and capsule/input fixes, Usage dashboard and provider-aware caching, limited opt-in awareness, updater/resource improvements and retirement of the legacy desktop coding Agent/Claude Console.

Synchronize all application version files and advance Linux packaging revision to151. Carry the previously validated CI optimization into the actual release source. Linux publication now requires explicit acceptance of the exact tag; this Beta will omit unaccepted Linux packages while preserving independent platform builds.

The complete public notes are in docs/releases/2.0.2-Beta.5-release-notes.md. They describe the incomplete accounting/perception scope and avoid guaranteed cache-rate claims.

Validation: all 167 frontend/contract test files and production build passed locally. CI contracts, release publication gates and actionlint passed. Final head 23054d3b1db1234b7817f406c69ad4551d26d9bc passed full platform CI and iOS tests/device build. The repository exact-source release CI verifier passed against the complete job report. The stale prompt-order integration contract exposed by the first Linux run was updated to assert the stable-prefix-before-context contract; all existing envelope and injection-defense checks remain. User has approved this desktop version and explicitly requested cloud Beta publication.

lvbaiqing added 30 commits November 6, 2026 23:51
lvbaiqing and others added 26 commits November 9, 2026 13:20
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 9, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

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

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-09T08:47:35.668922Z 23054d3 New commits
ℹ️ 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.

@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: 195b56ebe8

ℹ️ 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".

Comment on lines +457 to +458
Ok(recorder) => Some(Arc::new(recorder)),
Err(error) => { log::warn!("service usage unavailable: {error}"); None }

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 Provide an explicit reset path for an unreadable usage ledger

If service-usage.json cannot be decoded or validated, startup leaves usage_recorder as None. Both get_service_usage and clear_service_usage then reject with “service usage is unavailable,” while the Usage page only renders its clear control after successfully loading a snapshot. Consequently, even after the underlying storage problem is resolved, users cannot restore accounting without manually deleting the file. Wire the existing UsageLedger::reset operation into an explicit user-confirmed recovery action that remains available when the initial read fails, preserving the unreadable file until that action is requested.

Useful? React with 👍 / 👎.

@appergb
appergb merged commit 228e671 into beta Nov 9, 2026
20 checks passed
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