Skip to content

chore(release): cut v1.11.3 - #802

Merged
Y1fe1Zh0u merged 1 commit into
mainfrom
release/v1.11.3
Jul 28, 2026
Merged

chore(release): cut v1.11.3#802
Y1fe1Zh0u merged 1 commit into
mainfrom
release/v1.11.3

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Automated release PR for v1.11.3. Merging this PR will automatically tag the release and publish it.


v1.11.3 — Runtime safeguards and stability improvements

What's New

Core Features

  • Enforce L3 approval before Runtime workspace deletion
    • Adds a mandatory high-level approval gate for deleting Runtime workspaces, reducing the risk of accidental or unauthorized data loss.
  • Resume originating run after deletion approval
    • Automatically resumes the paused run once deletion is approved, streamlining operational workflows without manual intervention.
  • Group runs can reuse standard workspace tools
    • Enables group runs to access ordinary workspace tools, improving reuse and reducing duplication across workflows.

UI/UX Enhancements

  • Hide internal system tools from company settings
    • Removes non-user-facing tools from settings, decluttering the interface and reducing misconfiguration risk.
  • Clarify runtime budget in agent settings
    • Improves the label/description to make budget limits clearer for operators.

Optimizations & CI/CD

  • Automate production deployment after releases
    • Speeds up and standardizes production rollouts post-release, lowering human error and lead time.
  • Split Drone CI and tag-triggered deployment
    • Separates build/test from release deployments for safer, more predictable pipelines and clearer traceability.

Bug Fixes

  • Runtime stability and compatibility
    • Finalize v1.11.3 Runtime protocol fixes to resolve edge-case inconsistencies and improve interoperability.
    • Ensure Runtime migration remains compatible with existing Alembic storage, preventing upgrade interruptions on deployed systems.
    • Make Runtime maintenance recoverable across legacy group states, improving resilience during background tasks.
    • Keep fresh deployments compatible with logical deletion, avoiding startup or cleanup issues on new installs.
  • Upgrade and validation
    • Keep upgrade validation usable across a previously broken release path, ensuring smoother validation and rollback checks.
  • Integrations
    • Maintain PPTX document read compatibility with python-pptx, fixing failures when parsing PowerPoint content.
  • Chat
    • Fix chat history pagination to use a compound cursor instead of bare timestamps, eliminating duplicate/missing message pages under load.

Upgrade Guide

Standard steps (no manual database commands required; migrations run automatically on startup).

Docker

  • Update your environment to use the v1.11.3 image.
  • Run:
    docker compose pull
    docker compose up -d
    docker compose logs -f --tail=200
    
  • Wait for services to become healthy.

Source

  • From your deployment directory:
    git fetch --tags
    git checkout v1.11.3
    pip install -r requirements.txt
    npm install --legacy-peer-deps
    npm run build
    systemctl restart clawith.target
    
  • Verify logs and health checks.

Kubernetes

  • Update image tags to v1.11.3 in your manifests or Helm values.
  • Apply and wait for rollout:
    kubectl apply -f k8s/
    kubectl rollout status deploy/clawith-api
    kubectl rollout status deploy/clawith-worker
    
  • Confirm pods are Ready and passing health checks.

Notes

  • Runtime/Agent compatibility: This release includes final Runtime protocol fixes for the 1.11.3 line. Ensure all Runtime agents are updated in lockstep with the server to avoid protocol mismatches.
  • Automatic migrations: Database migrations run automatically on application startup; no manual steps are required.
  • Approval policy: Organizations relying on automated workspace teardown should account for the new L3 approval requirement to avoid unexpected pauses. Configure approvers as needed before rollout.

@Y1fe1Zh0u
Y1fe1Zh0u merged commit b20c708 into main Jul 28, 2026
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