lobehub v2.3.1

v2.3.1

🚀 Release v2.3.1

Added 17
  • Switch to auto approve directly from the approval card
  • Large-list multi-select and batch actions for tasks
  • Linear-style filters for tasks
  • Task-group create actions
  • Linear comment sync for tasks
  • Document favorites for pages
Changed 9
  • Page title and body are edited as one document
  • Drive handles large folders more smoothly
  • Paged activity for tasks
  • Paged wake records for channels
  • Faster desktop packaging
  • Connector restart and update improvements in desktop
Fixed 10
  • Duplicate approval submissions prevented
  • Duplicate tool execution on resume prevented
  • Stuck intervention continuations prevented
  • Page-agent rewrite issues fixed
  • Project restore and purge issues fixed
  • Structured-output issues fixed

From lobehub

From PR #22188: https://github.com/lobehub/lobehub/pull/22188

Summary

Contribution source: AI-assisted

🚀 LobeHub Release v2.3.1

Promote the complete current canary snapshot to main for a normal Stable release, replacing the closed, unmerged hotfix proposal #22186. This is not a two-commit hotfix.

  • Previous Stable: v2.3.0.
  • Canary snapshot: 1a6ba7ad3853f140cc5795c5baf5ae37f78c9a13.
  • Scope: 87 upstream commits/PRs, including both #22122 (auto approve) and #22069 (release publication token fix).
  • The release branch starts directly from that Canary snapshot, plus the bot-owned version bump and the Linux packaging repair in #22190. No hotfix cherry-picks or additional application features are layered on top.
Highlights
  • Approvals and agent reliability: switch to auto approve directly from the approval card; prevent duplicate approval submissions, duplicate tool execution on resume, and stuck intervention continuations. (#22122, #22058, #22060, #22068)
  • Tasks and Linear: large-list multi-select and batch actions, Linear-style filters, task-group create actions, paged activity, Linear comment sync, completed-issue imports, and background sync reliability. (#22055, #22083, #22136, #22155, #22087, #22086, #22050)
  • Pages, documents and files: title/body editing as one document, page-agent rewrite fixes, document favorites, drive downloads and folder ZIPs, and smoother large folders. (#22154, #22141, #22147, #22095, #22106)
  • Projects, channels and bots: project avatars and main-agent selection, project deletion confirmation, channel member picking, restore/purge fixes, paged wake records, and nightly bot retrospectives. (#22091, #22101, #22161, #22163, #22081, #22098)
  • Search, dashboards and models: DeepSeek search/crawling, sandboxed HTML widget cards, structured-output fixes, usage/cost accounting fixes, and official model-card metadata. (#21298, #22123, #21385, #22071, #22079, #22124)
  • Desktop and CLI: Copy Image, desktop shortcut listings, faster desktop packaging, connector restart/update improvements, and CLI v0.0.74. (#22067, #22113, #22121, #22165, #22166, #22179)
  • Rollouts and infrastructure: new-tier plan integration and percentage rollout support; the alternate rail layout remains behind im_layout. Release publication explicitly uses the App token so downstream publishing workflows can start. (#22115, #22143, #22003, #22069)
Upgrade and release sources
  • This release includes database migration 0199_topic_analyses.sql, adding the topic-analysis table, foreign keys and indexes. Self-hosted operators should include the normal database backup/migration procedure when upgrading.
  • Use the ordinary release initialization flow: resolve and pin the Cloud revision for this new release. Do not inherit the v2.3.0 hotfix Cloud pin.
  • Keep the exact title 🚀 release: v2.3.1 so the version bot and tag workflow agree on the intended version.
Test
Linux packaging repair (#22190)

The first Linux desktop build failed because electron-builder 26.16.1's template Snap target deleted chrome-sandbox from the shared linux-unpacked directory while AppImage was reading it. Windows passed; the macOS jobs were cancelled by matrix fail-fast.

  • Upgraded electron-builder to 26.18.0 and updated the isolated desktop lockfile, including the upstream fix electron-userland/electron-builder#10333.
  • Added an integration regression against the installed packager and real temporary files: fails with ENOENT on 26.16.1, passes on 26.18.0. Downloads/compressor execution are stubbed; real staging, filtering and filesystem mutations are exercised. The helper stays intact for other targets but is excluded from Snap inputs.
  • Changed-file lint, the regression and builtin-core packaging tests (2 passed), frozen-lockfile installation and git diff --check passed.
  • The repair was merged through #22190 because release/* branches require PRs; no branch protection was bypassed.
  • No new UI acceptance is needed for this build-tool-only repair. Full multi-platform packaging is being rechecked by the new PR CI run; the local tests do not claim a real installer build or launch.
Publication checklist
  • Release bot commits package.json version 2.3.1.
  • Required CI and review gates pass; merge this release PR into main without bypassing protection.
  • Auto Tag creates v2.3.1 and publishes the GitHub Release with ordinary source metadata.
  • Desktop Stable / Docker publishing completes, including installer and update-feed delivery.

A merged PR or a created tag alone is not proof that publication completed. No manual tag or release workflow dispatch was performed while preparing this PR.

🔗 Related Issue

Supersedes #22186 (already closed, not merged). Includes the full Canary range, rather than only #22122 and #22069.

Full change range: https://github.com/lobehub/lobehub/compare/v2.3.0...1a6ba7ad3853f140cc5795c5baf5ae37f78c9a13

View original

Upgraded? How did it go?

Discussion