* feat(cli): add standalone downloads and installers
* fix(cli): silence PowerShell download progress
* fix(cli): use framework APIs for Windows verification
* fix(cli): preserve null backup path during Windows updates
* docs(cli): translate native installation quickstart into Chinese
* refactor(agent)!: migrate sessions to Pi Durable
Replace patched AgentHarness storage with per-session SQLite and PostgreSQL commit mirroring. Migrate legacy history automatically and run agent queues with the main server.
BREAKING CHANGE: Remove standalone agent workers and return native Pi entry records from chat history APIs.
* fix(agent): constrain session log dialog scrolling
Keep the header visible and wrap long output while log entries and expanded records scroll within the dialog. Cover desktop and narrow viewports through the dashboard Sessions flow.
* fix(agent): hide entry IDs from session log card headers
Retain internal entry IDs in expanded raw records for debugging. Verify that card headers omit the IDs while raw JSON preserves them.
* test(e2e): handle browser wheel limits in session log checks
Verify that a normal wheel event moves the viewport before explicitly scrolling to the final record. Keep the dialog bounds, fixed header, wrapping, and expanded-record assertions.
* fix(agent): select model providers without inheriting unrelated auth
* fix(webui): prevent resize feedback when toggling agent panel
* test(agent): reproduce concurrent comment session races
* fix(agent): serialize comment sessions and deduplicate history
* docs(changelog): consolidate Pi Durable changes into one entry
* feat(workflow): migrate workflow engine from temporal to dbos
Replace Temporal and LocalExecutor with DBOS Transact (@dbos-inc/dbos-sdk) as the unified workflow engine. Background tasks, media transcoding, and AI agent workflows now execute with durable steps and task queues directly against PostgreSQL, eliminating the need for an external Temporal cluster and separate polling executors.
* fix(workflow): submit tasks via DBOSClient to allow enqueueing from steps
Enqueuing workflows using DBOS.enqueueWorkflowWithOptions threw a
DBOSInvalidWorkflowTransitionError when triggered from within a running
step or activity (e.g. creating embedding or autofill tasks during
video transcoding).
Use DBOSClient to submit and cancel workflow tasks directly against the
system database, detaching execution from the ambient workflow/step
context.
* feat(web): support SHUMAI_WORKERS environment variable
* fix(workflow): ensure CLI tasks are enqueued to DBOS and run DBOS migrations in global setup
- Initialize workflows and wait for pending DBOS submissions in shumai regenerate-embeddings CLI
- Remove no-op submit bypass and enqueue tasks via DBOSClient in producer and CLI contexts
- Add DBOS migration runner in test global setup to avoid concurrent migration deadlocks across test forks
- Update changelog and add regression tests
* fix(workflow): ensure unique per-instance executor identity for worker replicas
- Derive unique per-instance DBOS executor IDs across worker replicas
- Support SHUMAI_WORKER_ID, DBOS__VMID, and POD_NAME (Kubernetes Downward API)
- Disambiguate multi-replica bare metal/container deployments with host, PID, and instance suffix
- Prevent startup recovery from re-enqueueing workflows actively executed by other live workers
- Add multi-instance startup recovery tests and update deployment documentation
* fix(workflow): only register listened queues and update concurrency on change
- Only register queues that the executor instance actively listens to
- Use always_update conflict resolution so environment variable changes take effect on restart
- Prevent dedicated workers from overwriting unmanaged queue concurrency configurations
- Add tests verifying concurrency updates and queue isolation across worker roles
* refactor(workflow): simplify activities to use defineStep and direct calls (#482)
* refactor(workflow): simplify activities to use defineStep and direct calls
- Wrap activities using defineStep from @shumai/workflow-core
- Remove obsolete getActivities, registerActivities, dynamic activity proxies, and workerQueue arguments
- Remove executor.ts and registry.ts, consolidating workflow registration into workflow.ts
- Call activities directly across transcode and agent workflows
- Update all corresponding workflow tests and developer guide documentation
* fix(workflow): properly detect DBOSWorkflowCancelledError in runOnCancel fallback
- DBOSWorkflowCancelledError in DBOS SDK does not set name, inheriting 'Error'
- Implement isDbosWorkflowCancelledError checking instanceof, constructor.name, and dbosErrorCode
- Update unit tests to verify real DBOS SDK cancellation error instances
* docs(workflow): update documentation and readme for dbos migration
- Rename docs/configuration/temporal.mdx to docs/configuration/distributed.mdx
- Document DBOS-based distributed worker architecture and task queues
- Remove obsolete docker-compose/temporal/
- Update environment variables documentation in docs/configuration/env-variables.mdx
- Update references in README.md, README_CN.md, docs/docs.json, and related guides
* feat(deploy): implement KEDA ScaledJob and scale-to-zero On-Demand transcoding (#483)
* feat(deploy): add shumai-transcode docker image and k8s autoscaling example with garage s3
* docs(k8s): document port-forwarding and in-cluster s3 domain mapping
* feat(storage): support public s3 endpoint for browser uploads and update k8s example
* fix(k8s): configure s3 bucket cors rules in garage initialization
* fix(k8s): increase transcode worker memory limit to 4Gi for 4K video encoding
* feat(deploy): add AWS EKS deployment with Graviton3 Spot nodegroups and autoscaling
* docs(deploy): redesign EKS documentation, rename k8s to eks, and add scalable deployment feature
* docs: rephrase DBOS feature bullet to Durable Workflows via DBOS
* docs(eks): upgrade default instances to Graviton5 c9g.large and c9g.xlarge
* feat(eks): use On-Demand for general nodegroup and add spot capacity diversification
* docs(eks): fix Architecture diagram to locate all transcode worker pods in Transcode Compute Pool
* feat(deploy): implement KEDA ScaledJob and scale-to-zero On-Demand transcoding
* feat(transcode): support idle-timeout auto-drain for KEDA scaled jobs
* fix(deploy): fix EKS deployment manifests and documentation based on cluster verification
- Add centralized RAW file extension set and detection helper for 23 common camera RAW formats
- Update getProxyType and EXTENSION_MIME_TYPES to route RAW formats into the image pipeline
- Add exiftool-vendored runtime dependency and mark as external in build-npm script
- Implement embedded JPEG extraction to temporary file with priority JpgFromRaw2 -> JpgFromRaw -> PreviewImage
- Read and apply EXIF orientation from RAW container to prevent rotation/mirroring issues
- Integrate into TranscodeService.getImageInfo and transcodeImage with proper temporary file cleanup
- Add hasUsablePreview guard in transcodeImageWorkflow to gracefully handle RAW files without embedded previews
- Add unit, service, workflow, and E2E tests for RAW processing
Checks if the container is running as root (UID 0) before executing
chown and gosu. If running directly as a non-root user (e.g. in hardened
environments like Kubernetes runAsNonRoot or via docker run --user),
it directly execs the command, preventing EACCES and permission errors.
This updates the Dockerfile and adds a scripts/docker-entrypoint.sh script.
Under native Linux (like Debian), when docker-compose mounts a host folder
as a volume (e.g. `./data:/app/data`), and the folder doesn't exist, the
docker daemon creates the folder as root-owned (`root:root`).
Because the container runs as a non-root user `bun`, it gets permission
denied (`EACCES`) when trying to write to the data directory.
To resolve this in a beginner-friendly way without manual host-side
permissions updates:
1. The runner stage now installs `gosu`.
2. At the end of the Dockerfile, the user switches back to `root` so the
container launches as root.
3. On launch, the entrypoint script executes. Since it runs as root, it
automatically changes ownership of `/app/data` to `bun:bun`.
4. The entrypoint script then uses `gosu` to drop privileges and launch the
actual server processes as the non-root `bun` user.