Skip to content

v1.11.2

Choose a tag to compare

@github-actions github-actions released this 23 Jul 13:54
· 194 commits to main since this release
6a4e8ca

v1.11.2 — Group creation enhancements and runtime reliability

What's New

Core Features

  • Select members during group creation
    • You can now pick group members at the time you create a group, streamlining setup and reducing follow-up steps.
  • Unified workspace formats for groups and agents
    • Groups now support the same workspace formats as agents, providing a consistent collaboration experience and simplifying content sharing.
  • Preserve history on deletion of models and agents
    • Historical activity and references remain intact when models or agents are deleted, improving auditability and preventing accidental loss of context.

Optimizations

  • Faster, single-pass group greetings
    • Simple group greeting flows run in a single pass, reducing latency and improving responsiveness during onboarding.
  • Faster CI image builds
    • Image builds now use a faster Alpine mirror, shortening build times in CI pipelines and reducing release turnaround.

UI/UX Enhancements

  • Planned group collaboration stays visible
    • Planned collaborative actions remain visible to all group members, improving transparency and coordination.
  • Cached group announcements persist across tab switches
    • Announcement content no longer disappears when switching tabs, ensuring consistent visibility across the app.

Bug Fixes

  • Restored automatic execution for Agent task schedules
    • Fixes a regression where scheduled agent tasks were not executing automatically, restoring expected automation behavior.
  • Restored reliable runtime and end-to-end behavior
    • Addresses multiple stability regressions to ensure predictable runtime and E2E test behavior in v1.11.2.
  • Prevented deterministic compaction failures from poisoning retries
    • Runtime retries are no longer affected by deterministic compaction failures, improving overall task reliability.
  • Stopped invalid request budgets at compact input boundary
    • Adds guardrails to block invalid request budgets before compaction, preventing downstream errors and wasted cycles.
  • Prevented image payloads from failing before provider dispatch
    • Image payloads are correctly prepared and dispatched to providers, reducing pre-dispatch failures.
  • Preserved backend error semantics across user-visible surfaces
    • Error semantics are consistent across backend and UI layers, improving clarity and debuggability.
  • Preserved human assignments before group planning
    • Human role assignments remain intact when initiating group planning, preventing unintended loss of ownership.
  • Kept completed group plans from disappearing silently
    • Completed plans no longer vanish without feedback, improving traceability and user confidence.
  • Kept oversized file generation recoverable
    • Oversized file generation now fails gracefully and remains recoverable, reducing disruption in long-running tasks.

Upgrade Guide

Docker

  • Update services to v1.11.2 and restart:
docker compose pull
docker compose up -d

Source

  • Upgrade to the v1.11.2 tag, rebuild the frontend, and restart services:
git fetch --tags
git checkout v1.11.2

# Install/update dependencies
npm ci
npm run build

# Restart your application processes (example)
systemctl restart clawith || pm2 restart all

Kubernetes

  • Deploy the v1.11.2 image and restart workloads:
# Update image tag in your manifests to v1.11.2, then:
kubectl apply -f deploy/
kubectl rollout restart deployment/clawith
kubectl rollout status deployment/clawith

Notes

  • Node runtime compatibility
    • Release checkout now enforces a supported Node runtime. Ensure your CI and build environments use a current, supported Node LTS.
  • CI and tooling
    • Release notes workflow and GPT model updated; test branches are constrained to deployable source to improve pipeline reliability.
    • Faster Alpine mirror is used during image builds; no configuration changes are required for standard setups.
  • No manual database migrations
    • Database migrations run automatically on application startup. No manual steps are required.