Skip to content

Releases: Rubiss-Projects/ai-assistant

Release v1.27.0

Choose a tag to compare

@github-actions github-actions released this 16 Oct 18:43

OpenCode now uses V2 only, with @opencode/cli pinned to 2.0.31 in the image. Native installs require V2 2.0.31 or newer.

  • Convert generated agents, permission rules, MCP configuration, and classifier effort settings to V2.
  • Own a private server for each conversation turn and wait for all enabled MCP servers before inference.
  • Keep shared-mode ambient configuration isolated, preserve unrestricted legacy permission policies, and recognize API-key authentication in status.
  • Transfer only credentials into the classifier's disposable database.
  • Include the dependency updates merged since v1.26.0 (Copilot/Codex/MCP SDKs, Playwright, dotenv, cron-parser, and Node typings).

Existing OpenCode V1 sessions and credentials migrate when V2 opens their persistent data directory. Back up that directory and assistant session maps before upgrading. A V1 rollback requires restoring compatible pre-upgrade data; do not open a V2-migrated database with V1. Native users should replace opencode-ai with @opencode/cli and update OPENCODE_BIN if set. Shared mode excludes ambient global/project provider definitions; unrestricted mode retains supported V1-format configuration.

Validation: 733 Linux tests, build, production-image runtime CI, actual V2 CLI/tool and permission checks, and a separate V1 session/credential migration fixture.

Application PR: #127
Container: ghcr.io/rubiss-projects/ai-assistant:v1.27.0 (linux/amd64 and linux/arm64)

Release v1.26.0

Choose a tag to compare

@github-actions github-actions released this 02 Oct 10:53

Slack can now deliver generated files and keep channel, thread, and allowlisted direct-message conversations in separate sessions. Top-level mentions reply directly in the channel; threaded mentions stay in their parent thread.

  • Deliver provider-generated files, including file-only responses, with cancellation and restart recovery. Interrupted deliveries are retained for reconciliation rather than automatically retried.
  • Expose secure file-download and video-transcode tools for Slack, alongside attachment registration.
  • Add host-derived chat classification for Slack conversations, rejecting inconsistent thread identities during replay.
  • Configure Codex hosted web search with CODEX_WEB_SEARCH_MODE (disabled, cached, indexed, or live; default cached). This is separate from sandboxed-command network access.
  • Convert empty legacy read-only Codex credential-directory placeholders into directories while preserving ambiguous files and rejecting symlinks.
  • Update MCP SDK, dotenv, and Node types, and move the Docker build cache to GHCR.

Slack setup: add the files:write bot scope for response uploads. Replies inside DM threads are unsupported; send a top-level DM instead. For direct messages, add im:read and im:history and subscribe to message.im. Reinstall the Slack app after changing scopes. Restart the application after changing the Codex search setting.

Container image: ghcr.io/rubiss-projects/ai-assistant:v1.26.0 (linux/amd64 and linux/arm64).

PR: #110

Release v1.25.2

Choose a tag to compare

@github-actions github-actions released this 30 Sep 05:43

Fixes Discord chats failing after a Codex upgrade:

  • Existing workspace credential placeholders are preserved and remain inaccessible to agent tools.
  • Conversation handoffs accept Codex's nonfatal model-change warning while retaining tool restrictions and summary validation.

Conversation history is preserved; no session reset is required. Deploy all AI Assistant containers with this same release.

Validated with 664 tests, a TypeScript build, container sandbox checks, and real CLI model-change/resume coverage. See #109.

Container image: ghcr.io/rubiss-projects/ai-assistant:v1.25.2 (linux/amd64 and linux/arm64).

Release v1.25.1

Choose a tag to compare

@github-actions github-actions released this 30 Sep 04:51

Upgrade the bundled Codex CLI and SDK to 0.159.2, enabling gpt-6.1-sol with max reasoning through ChatGPT authentication.

Container image: ghcr.io/rubiss-projects/ai-assistant:v1.25.1 (linux/amd64 and linux/arm64).

Fresh shared workspaces prepare the credential directories reserved by the newer CLI before applying the existing deny rules. Those directories remain inaccessible to the sandbox; no credentials are copied into them.

Set CODEX_MODEL=gpt-6.1-sol and CODEX_REASONING_EFFORT=max to select the new model. For the isolated reviewer, use the corresponding CODEX_REVIEW_MODEL and CODEX_REVIEW_REASONING_EFFORT settings.

No data or session migration is required from v1.25.0. All three assistant containers must use the same release.

Application PR: #108

Release v1.25.0

Choose a tag to compare

@github-actions github-actions released this 28 Sep 05:43

Container image: ghcr.io/rubiss-projects/ai-assistant:v1.25.0 (linux/amd64 and linux/arm64).

  • Fix Cut release staying disabled after merge: refresh now accepts GitHub's valid comparison URL and prepares the release preview.
  • Bundle a contribution-specific babysit-pr workflow covering fixes, published replies, refreshed thread versions, resolution, and current-head review/CI checks. Public read-only CI results require no new GitHub App permissions; private job logs and reruns remain human operations.
  • Add the Ready for review action and /github ready, with linked-account authorization and public Discord confirmations for successful actions.
  • Forward authenticated Slack attachments to agent providers.

Validation: all 663 Linux tests, build, and production container-runtime checks passed. No session-storage migration or additional App permission is required.

PRs: #104, #106, #107.

Release v1.24.0

Choose a tag to compare

@github-actions github-actions released this 27 Sep 21:27

Approve, merge, and release bot-created pull requests from their Discord thread using each person's own linked GitHub account.

  • /github link privately connects your account with GitHub Device Flow; /github unlink revokes the bot's local link. Actions never fall back to the operator's identity.
  • Contributors can submit their own approval. Merge and release also require explicit bot capabilities and GitHub repository permissions.
  • Action cards verify reviewed revisions and checks, persist receipts, and reconcile uncertain responses across restarts.
  • Release cards preview the version, exact commit, and all changes since the previous release. Publication uses the fixed release workflow; deployment remains a separate reviewed Docker promotion.

Also includes the unreleased startup fix that skips Discord command registration for Slack-only containers.

Operators: configure a separate GitHub App with Device Flow and expiring user tokens, set GITHUB_USER_APP_CLIENT_ID, and enable AI_ASSISTANT_ENABLE_GITHUB_ACTIONS. Shared-mode contributions and server-side Codex reviews are required. Grant github.merge and github.release explicitly in the rights configuration. Back up the entire private github-actions state directory, including its encryption key. No session migration.

Validation: 614 Linux tests, TypeScript build, and build/container CI passed.

Container: ghcr.io/rubiss-projects/ai-assistant:v1.24.0 (linux/amd64 and linux/arm64).

Changes: #103

Release v1.23.1

Choose a tag to compare

@github-actions github-actions released this 27 Sep 18:54

AI Assistant now recovers journal ownership automatically after a crash or forced termination. A live worker still excludes competing processes and containers, even when their process IDs match. Interrupted turns remain recorded without being automatically repeated.

Uses the existing SQLite dependency for an OS-backed lock and atomic ownership markers. No turn-record migration or new dependency is required. Never delete the persistent owner.sqlite file. Clean upgrades need no intervention; a stale owner.lock from an older release still requires confirming all workers are stopped before archiving that legacy marker.

Validated with all 580 tests, the production-container CI checks, and an isolated Docker forced-kill/restart test with PID reuse.

Application PR: #102

Container image: ghcr.io/rubiss-projects/ai-assistant:v1.23.1 (linux/amd64, linux/arm64).

Release v1.23.0

Choose a tag to compare

@github-actions github-actions released this 27 Sep 13:41

AI Assistant now routes conversations through a shared service, with durable turn admission, ordering, deduplication and separate generation/delivery handling. Discord retains its existing session keys and features.

  • Add an opt-in Slack adapter for explicit mentions, threaded replies, bounded authorized history and audience checks before delivery.
  • Add local interactive and one-shot CLI conversations with real or fake providers, isolated session state, JSON output and reset support.
  • Improve cancellation and startup/shutdown cleanup across adapters and providers.
  • Expire completed turn records after seven days and cap each journal at 10,000 records; interrupted deliveries have the same seven-day reconciliation window, while retryable generated replies remain for recovery. New turns are rejected when capacity is reached.

Discord remains the default. No configuration change or session-store migration is required for the existing Discord deployment. Slack requires separate credentials and explicit user/channel allowlists; its text-only limitations and recovery procedures are documented in the README. Adapter journals must remain outside provider-readable workspaces.

Validation: 574 Linux tests passed with no skips; production container checks passed; compiled CLI persistence, isolation, reset and interactive flows passed; a real Codex CLI request passed under production sandbox restrictions. Slack was tested using fixtures; live Slack was not tested because no Slack credentials are configured.

Changes: #96

Container image: ghcr.io/rubiss-projects/ai-assistant:v1.23.0 (linux/amd64 and linux/arm64). Update the assistant, browser and reviewer together. Previous production version: v1.22.1.

Release v1.22.1

Choose a tag to compare

@github-actions github-actions released this 26 Sep 23:30

Conversation refreshes now receive their saved GitHub contribution IDs and PR URLs directly from the host, so continuing an existing PR no longer depends on the handoff summary retaining those references.

Ownership remains scoped to the Discord requester, server, and conversation. No data migration or configuration changes are required.

Changes: #99

Container image: ghcr.io/rubiss-projects/ai-assistant:v1.22.1 (linux/amd64 and linux/arm64). Update the assistant, browser, and reviewer together.

Release v1.22.0

Choose a tag to compare

@github-actions github-actions released this 26 Sep 21:05

Rook can now install npm dependencies, build TypeScript, and run its full test suite inside shared-mode Codex sessions.

  • Allow package downloads from registry.npmjs.org and include native build tools and local Node headers.
  • Keep development copies and npm state in private executable session scratch; preserve workspace credential restrictions.
  • Add npm run check with temporary test state, sandbox-local fixtures, and bounded test concurrency.
  • Upgrade Codex to 0.157.1 for confined Linux Unix socket support.
  • Verify clean installation, build, all 483 tests, and blocked credentials/host services in container CI.

Container image: ghcr.io/rubiss-projects/ai-assistant:v1.22.0 (linux/amd64 and linux/arm64).

Previous deployment/rollback: v1.21.0. No application session-store migration.