Feedbacks v0.2.3

Feedbacks v0.2.3

Source commit: 1bbdbab

• Application and source: 0.2.3
• Chrome extension: 0.1.60
• Codex and Claude Code plugins: 0.2.3

These components have separate version schemes. The Git tag follows the application version.

• Refresh the locked MCP server/client SDK and Vite build tooling to patched compatible versions; the current lockfile passes npm audit.
• Package the current application with extension 0.1.60 and Claude Code/Codex plugins 0.2.3, including context-efficient task reads and updated review guidance.
• Recover task handoff with a manual-copy dialog when a browser clipboard permission request never completes.
• Repair review controls inside native modal previews and clarify stale project access and General-project fallback.
• Add optional browser sign-in for HTTP MCP clients with own-server OAuth; local stdio plugins and personal project-scoped keys remain supported.
• Keep recording, diagnostic and public-website documentation aligned with the current review workflow. State official plugin-directory review status separately from direct installation.

Upgrade from 0.2.1 or the unpublished 0.2.2 preparation

Back up PostgreSQL and private object storage, and verify a restore before upgrading. Preserve the database volume, ORGANIZATION_ID, storage bucket/prefix and existing encryption secrets. Pin the new application image by its published digest; pull it and run docker compose up -d --wait using the existing private environment. Startup applies pending migrations. Verify sign-in, one synthetic screenshot upload/readback and an allowed agent read before handing the server back to the team. Do not use docker compose down -v.

OAuth is opt-in (MCP_OAUTH_ENABLED=true) and requires your own HTTPS deployment; existing URL/key connections continue to work. Existing personal keys retain their original projects and scopes. The extension retains saved server connections. This application release does not submit or publish an extension to the Chrome Web Store or a plugin to an official directory.

Compatibility and known limits

One installation serves one organization; public registration, billing, SSO and shared-database customer tenancy are not included. Recording coverage depends on the explicitly enabled channels and browser support. Keep the previous image digest and a compatible database/storage backup pair for recovery; an older image is not guaranteed to understand a migrated database. See operations, self-hosting and release guidance.

Assets include the reviewed source export, public extension ZIP, standalone plugins and CycloneDX dependency inventory. Verify SHA256SUMS before installation. Container registry publication, hosted deployment and Chrome Web Store upload/review are separate steps.

Published Docker images and direct installation

Both softinator/feedbacks:0.2.3 and softinator/feedbacks-site:0.2.3 provide Linux AMD64 and ARM64 images, native smoke checks, SBOM and provenance. Image source labels match the application revision above.

docker pull softinator/feedbacks:0.2.3

Deploy the release Compose with your private environment and a trusted HTTPS reverse proxy: self-host guide. For production pin the application to:

softinator/feedbacks@sha256:c009ad90d1454b74f953c9d401b684837465948068f6d69fffd830bc428c6827

The separately checksummed image-manifests.json records both images. The original SHA256SUMS and its release assets are unchanged.

Direct Claude Code/Codex marketplace and portable MCPB. Official Anthropic publication and OpenAI desktop local-MCP submission access remain under their respective reviews; direct installations are available.