Skip to content

Releases

LockBot v3.3.2

Choose a tag to compare

@dynamicheart dynamicheart released this 17 Nov 03:57

LockBot 3.3.2

Agent API group notices again show the title, user, and command, with the preset task category when supplied. Only confirmed changes produce a notice.

This patch uses the existing configuration, data volume, and credentials.

LockBot v3.3.1

Choose a tag to compare

@dynamicheart dynamicheart released this 17 Nov 03:03

LockBot 3.3.1

Patch release from v3.3.0.

  • Agent API group notices report confirmed changes. Rejected requests keep their API reply and produce no group notice. Booking notices identify the booking queue. Release notices identify the resources actually affected.
  • Device bots release the complete set of nodes in a whole-node batch. The command still releases only the caller's own holdings.
  • Lock replies omit the personal workbench link. The configured Skill promotion and the explicit help entry remain available.

The patch uses the existing data volume and configuration. It introduces no schema migration or credential rotation.

v3.3.0

Choose a tag to compare

@dynamicheart dynamicheart released this 14 Nov 04:54
2576438

Highlights

  • Personal resource dashboard with confirmed browser sessions and explicit source labels.
  • Discover same-identity bot bindings and recover stored per-bot personal keys, with strict service/platform identity boundaries.
  • Improved monitoring alignment and caller labels.
  • Deployment-specific Skill URL embedded consistently in Markdown and installation bundles.

Upgrade

Keep the existing data volume, instance identity, JWT/encryption keys and personal keys. API version remains 1. The database adds a nullable encrypted credential-copy field; existing keys remain valid. Historical digest-only keys become recoverable when their holders present each key to the recovery endpoint.

The personal dashboard is opt-in using LOCKBOT_PERSONAL_PANEL_CONFIG. Organization-specific report adapters are separately maintained and are not included in this release. See docs/design/personal-resource-panel.md and docs/agent-api/credential-recovery.md.

Commit: 2576438. Release-candidate and merged-commit CI passed. Publication workflows and deployment outcomes are tracked separately; this note does not claim a completed formal rollout.

3.2.0

Choose a tag to compare

@dynamicheart dynamicheart released this 30 Oct 17:51
b43e2dc

Lockbot 3.2.0 adds public allocator lifecycle evidence and a bounded OP history consumer, scoped audit-credential management, durable audit-read summaries, typed messaging credentials and default-off Feishu reactions, membership notices and in-place query panels.

Fixes include compact Feishu notices, addressed rich-text/code-block feedback, private history projections, traffic chart selection geometry, authenticated resource no-store responses and narrow metric process layouts. Infoflow remains supported and API version remains 1.

Validation: the final chart PR passed six required checks on its current head and base. Actual test-service command/reaction/panel/audit and bound-group remove/re-add acceptance are recorded in the roadmap. The installed six-command history exercise returned eight committed events across nine frozen pages; insufficient starting coverage remains unknown with null totals, not resource-hours.

Upgrade: preserve the original data volume, JWT/encryption/metrics keys, port and configuration. Optional Feishu features remain off unless explicitly enabled. Platform migration is deferred and is not implemented by this release. Docker/PyPI/telemetry publication and offline-image artifact builds succeeded. Formal deployment completed on 2026-10-31, preserving the original service port, data volume, keys, configuration,39 bots,26 running bots,15 bindings and active locks/queues. Actual privacy, registry, metrics and single-receiver handshake checks passed. Image artifact13000176833 SHA-256: eb39fdf1b0efebb0818e5477fd45a184fdc2552102f998a0487b18eeb8429436. No new formal-group resource commands were exercised by this upgrade.

3.1.0

Choose a tag to compare

@github-actions github-actions released this 29 Oct 17:39
8eba15c

Lockbot 3.1.0

Changes

  • Add dedicated, revocable task_notes:read audit credentials issued only by a current super administrator. Ordinary OP, personal and management tokens cannot substitute for this credential on the new audit routes.
  • Read bounded Agent operation notes or verified live declarations for explicitly authorized bot identities. Search and pagination use a narrow projection; disclosure evidence commits before notes are returned.
  • Use wide utilization cells for host metrics and the ordered device list, with a stacked narrow-screen fallback. Bot details remain full width.

Compatibility

The audit API is additive (version 1). An additive audit_credentials table stores token digests and scoped delegation metadata; existing credentials, bot settings and resource state retain their formats and permissions. No credentials are automatically issued. Existing Infoflow/Feishu messages and resource operations are unchanged. This is not the complete lifecycle audit in issue #54.

Feishu reaction replies (#68), in-place queue panels (#62) and membership onboarding (#63) are not part of this release. Corporate application approval and permission publication remain separate human decisions.

Validation and rollout

PR #66 passed all six required checks at 87fd41b; independent review tests passed 59 cases. PR #67 passed all six checks on synchronized head 994c02e. Real HTTP validation on 8002 exercised history/live reads, cross-bot and credential-family denial, rotation, revocation and default public projection with a temporary test credential, revoked afterward.

Formal production is still 3.0.2 at preparation time. Publication, image download/checksum verification and formal upgrade acceptance are separate gates. Track final evidence in roadmap issue #27 and issue #56.

See delegation protocol and consumer examples.

3.0.2

Choose a tag to compare

@dynamicheart dynamicheart released this 29 Oct 16:52
eccb4d1

Preserve full-width bot details on wide displays. Cluster-status content retains compact ordered device rows, and detailed Agent history keeps public task categories with separate Agent and note captions.

Includes the 3.0.1 task-history correction and refreshed deployment/platform documentation. Existing Infoflow replies, Feishu replies and task-access permissions are unchanged. No database migration.

The formal service upgrades directly from 3.0.0; the 3.0.1 tag remains unchanged. CI and integration evidence are linked from PRs #61 and #65.

3.0.1

Choose a tag to compare

@dynamicheart dynamicheart released this 29 Oct 16:43
8c1f740

Fixes public task categories disappearing when detailed Agent notes are enabled. Agent labels and notes now have separate captions, and bot details use a bounded, denser layout.

Ordinary users, bot administrators and existing OP credentials retain the same restricted task projection. No database migration is introduced.

Validation: all six PR CI checks passed on efb214e. The 8002 integration service was verified in the browser.

Changes: #59, #61. Production rollout is tracked separately from publication.

v3.0.0 — Feishu and Infoflow

Choose a tag to compare

@dynamicheart dynamicheart released this 29 Oct 16:06
80cc6a5

Highlights

  • Support Feishu alongside Infoflow: one enterprise application, independently managed resource groups, HTTP or WebSocket receiving, dedicated proxy configuration, native mentions and links.
  • Add centrally managed application credentials, audited Secret viewing/rotation and safe deletion; clarify enterprise permissions and Agent-assisted deployment.
  • Improve resource/queue administration, platform filters, Agent operation history, scoped service monitoring and compact broadcasts.
  • Retain public task categories while restricting detailed notes to their owner and explicitly authorized super-administrator reads. Ordinary OP keys do not inherit detailed-note access.

Upgrade

Preserve the original data volume, encryption/JWT keys and metrics signing configuration. Use a single process; do not run duplicate receivers against the same application. Existing Infoflow bots, personal keys and Agent API routes remain supported. Feishu uses additive application/route/deduplication tables; this is not a rewrite of existing Infoflow credentials or a shared cross-platform resource pool.

Corporate application permissions/publication require administrator review before submission. Test-enterprise credentials must not be copied into production. Database readability alone does not guarantee a lossless downgrade of Feishu or privacy behavior.

Validation: reviewed integration passed 1,820 backend tests (7 skipped), 170 frontend tests, six required CI checks, affected API/browser checks and earlier real two-group/rendering acceptance. The release preparation PR also passed its own six required checks and both telemetry bundle builds.

Images and offline artifacts are built from tag v3.0.0; consult completed workflow results before deployment. Further credential migration, full audit lifecycle APIs and delegated detailed-note credentials are tracked separately in #57, #54 and #56.

Lockbot v2.15.2

Choose a tag to compare

@github-actions github-actions released this 29 Oct 08:41
f4badac

Lockbot v2.15.2

A maintenance release for reliable Agent notifications and stricter private-task access.

  • Flush Agent operations collected during the notification throttle window in trailing batches instead of silently dropping them. Keep notification failures separate from the resource operation result; uncertain notification delivery does not replay a lock or release.
  • Limit private task purposes, Agent labels, authorization notes and credential identifiers to the same verified actor or the current super administrator. Ordinary bot administrators and bot-scoped OP keys retain public categories, resource state and safe operational summaries.
  • Apply server-side filtering to management state, activity, authorization audit and legacy log downloads; audit elevated reads without copying private task bodies. Refresh Agent/OP Skills and context privacy metadata.

Delivery remains best effort: trailing batches use a bounded in-process queue and do not survive a process restart.

Compatibility: no new database migration or key rebind is required. The ordinary OP/admin visibility restriction is intentional; an OP key generated by a super administrator remains an ordinary bot maintenance credential. Hardware metrics authorization and approved container/host-user metadata remain separate. App RBAC is not encrypted isolation from OS/root or platform signing-credential holders; private notes must not contain secrets.

Scope: includes the fixes from #42 and #40 on release/2.x. The scoped monitoring/history work (#22), OP historical reports (#44) and Feishu work are not included. Existing deployments must upgrade explicitly; keys do not need to be rebound. Rolling back old code may restore the earlier disclosure behavior, so retain the privacy fix during incident recovery.

v2.15.1

Choose a tag to compare

@dynamicheart dynamicheart released this 29 Oct 06:31
f8cb2a2

Improvements

  • Unify resource tables in the public read-only page and bot detail. Keep remaining lease time beside its holder, remove nested overview scrolling and repeated per-card timestamp tooltips, and summarize source freshness and affected nodes.
  • Move data-source setup into bot configuration information. Add Lockbot/DCGM/custom templates and node/device mapping rows, with browser-local validation.
  • Add available host memory and buffers/cache counters without increasing the five-minute hardware sampling rate. Missing supplemental counters remain unknown.
  • Publish versioned Linux amd64/arm64 telemetry deployment bundles with verified official Prometheus binaries, exporter, protected gateway, offline dependency wheel, manifests, checksums, systemd examples and an Agent deployment runbook. Remove the obsolete xpu_monitor example.
  • Signal reported Skill/API compatibility on personal API responses, including handled errors. Maintain legacy request compatibility; clients reload verified instructions before the next mutation and must not replay completed commands.
  • Reject malformed nonempty commands instead of silently returning a resource query.

Compatibility and limits

API major version remains 1. Existing keys, bot configuration, holdings and bookings remain supported. Source connectivity is checked independently by each browser or Agent; an administrator's connection test cannot guarantee another client's access. Hardware telemetry is best effort and never controls resource ownership. Cache size alone does not diagnose driver OOM.

Linux amd64 bundles include an offline-install smoke test; arm64 packaging is verified but real arm64/NVIDIA environments require their own acceptance. Separate trust domains need isolated source credentials; do not copy the existing global HMAC signing key into a second environment. The H20 private-network integration remains separate and no VPN or network ACL changes are included.