AutoSign 0.18.3

Highlights\n\n- Added a dedicated calendar-and-check favicon for the Web UI.\n- Improved Baidu Tieba batch sign-in safety: fixed pacing, detection of CAPTCHA/login/rate-limit signals, and a safe stop for unattempted forums.\n- Updated execution details and notifications for interaction-required outcomes.\n\n## Verification\n\n- Full Python test suite: 250 passed.\n- Ruff check for product source and tests passed.\n- linux/amd64 image build and isolated container smoke test passed.\n\n## Notes\n\nThis release does not include private NAS deployment artifacts, configuration, keys, account data, or backups.

AutoSign v0.18.0

Highlights

• Simplifies plugin SDK, execution, Vault, notification, and interactive-browser boundaries.
• Extracts authenticated API routers for auth, accounts, browser sessions, backups, notifications, and execution history.
• Splits Accounts, History, Browser, and Notifications frontend domains into focused authenticated assets.
• Adds bounded VikACG recovery handling and preserves encrypted browser-state compatibility.
• Revalidates SignResult.model_copy() results so updates cannot bypass status invariants.

Compatibility

• Database schema and encrypted browser-state format are unchanged.
• Existing accounts, schedules, notification assignments, backups, and NAS data mounts remain compatible.
• Preserve the existing .env, AUTOSIGN_MASTER_KEY, and data directory when upgrading.

Verification

• Independent staged review completed.
• Local Ruff, frontend syntax checks, and 184 tests passed.
• Wheel/image asset inclusion, isolated Docker health, authenticated boundaries, noVNC assets, persistence, and restart behavior were verified.
• User reported manual NAS and account acceptance passed before publication.

See PR #6 for the reviewed change history. Private NAS images, Compose files, logs, credentials, and deployment-specific paths are intentionally not attached to this public Release.

AutoSign v0.17.0

Highlights

• Separate bounded capacity pools for scheduled browser automation and interactive login.
• Serialized browser cold start and deterministic cleanup for contexts, native Chromium processes, temporary profiles, and capacity leases.
• Account execution/deletion lifecycle gating to prevent concurrent-use races.
• Bounded administrator login-rate tracking and an authenticated, privacy-safe runtime status view.
• Version consistency checks across package metadata, runtime version, and the health endpoint.
• Browser route diagnostics for partially loaded pages and stale fixed CDN routes.

Validation

• DeepSeek reviewed the fixed implementation commit with no P0/P1/P2 blockers.
• Ruff and 152 pytest tests passed locally.
• Push, pull-request, and merged-main GitHub Actions passed for the published commits.
• The user completed NAS functional acceptance and final sign-in verification.

Upgrade notes

• No database schema migration is introduced by this release.
• New browser capacity defaults are automation 2 and interactive 1; lower automation capacity on memory-constrained hosts if necessary.
• Keep deployment-specific proxy addresses, bypass rules, fixed DNS entries, credentials, data, and image archives outside the public repository.

Full Changelog: v0.16.0...v0.17.0

AutoSign v0.16.0

What's Changed

• Harden runtime lifecycle and persistence in 0.16.0 by @Adrenaline036 in #4

Full Changelog: v0.15.3...v0.16.0

AutoSign v0.15.3

AutoSign v0.15.3

本版本集中修复浏览器登录状态刷新问题，并为交互登录增加安全粘贴支持。

新增

• noVNC 实时登录支持 Ctrl+V、右键菜单及移动端长按粘贴
• 实时页面顶部提供默认隐藏内容的备用粘贴输入框
• 截图交互模式支持整段文本粘贴
• Playwright 使用 keyboard.insert_text() 原样输入中文与密码符号

修复

• 自动签到成功后保存网站刷新后的 Cookie、localStorage、sessionStorage 与 IndexedDB
• VikACG 失效旧状态不再导致交互登录循环刷新
• VikACG 正确识别普通“已经签到”页面状态

安全

• 粘贴复用现有管理员会话、CSRF 和长度校验
• 粘贴内容不写入数据库、通知或成功提示
• 备用输入框发送后立即清空
• 失败执行不会覆盖最后一份可用浏览器登录状态

验证

• 87 项自动化测试通过
• GitHub Actions 通过
• DeepSeek 独立代码审查通过
• Linux/amd64 Docker 镜像健康检查通过
• NAS 实际部署与粘贴流程验收通过

Release 不附带任何私人 .env、数据库、浏览器状态、NAS Compose 或代理配置。请从源码构建，或使用自己保存的本地部署产物。