- Changed the Discord link to point to the new URL: https://discord.tinyhumans.ai/.
- Added a new "Highlights" section detailing key features of OpenHuman, including Neocortex, The Subconscious, Screen Intelligence, and more, with links to their respective documentation.
These updates improve the clarity and accessibility of the README, ensuring users have the latest information and can easily navigate to important features.
- Bumped the OpenHuman package version to 0.52.24 in both Cargo.lock files.
- Updated the Content Security Policy (CSP) in tauri.conf.json to allow connections from localhost and 127.0.0.1, improving development flexibility.
These changes ensure compatibility with the latest OpenHuman features and enhance security settings for local development.
- Updated the release workflow to include signing of macOS .app tarballs with the Tauri updater key, ensuring integrity for installed clients.
- Modified the upload script to handle the signing process and added error handling for missing signing keys.
- Removed Linux x86_64 asset handling from the updater manifest to streamline the release process.
These changes improve the security and reliability of macOS artifact uploads in the release workflow.
- Commented out the Ubuntu 22.04 platform configuration in the release.yml file to streamline the workflow and focus on active platforms.
- This change helps maintain clarity in the release process by reducing clutter from unused configurations.
- Replaced the existing public key in the Tauri configuration file with a new one to ensure proper functionality of the updater plugin.
- This change is necessary for maintaining the integrity and security of the update process within the application.
- Updated the release workflow to include caching for the vendored `tauri-cli` binary and its installation metadata, improving build efficiency across platforms.
- Modified the `ensure-tauri-cli.sh` script to restore the cached binary if available, reducing installation time and ensuring the correct version is used.
- Changed the build script to utilize `cargo tauri build` instead of `npx tauri build`, aligning with the new CLI setup for better integration with the CEF-aware environment.
These changes streamline the development workflow and enhance the reliability of the Tauri setup.
- Added back the previously commented-out configurations for Ubuntu 22.04 and Windows in the release.yml file, allowing builds for these platforms to be included in the release process.
- Updated the arguments, targets, and artifact suffixes for both platforms to ensure proper handling during the release workflow.
These changes enhance the cross-platform support in the release process, ensuring that builds for Ubuntu and Windows are correctly generated and published.
- Added a new script `ensure-tauri-cli.sh` to ensure the vendored CEF-aware `tauri-cli` is installed, preventing runtime errors related to missing Chromium Embedded Framework files.
- Updated `package.json` scripts to call `yarn tauri:ensure` before other commands, ensuring the correct CLI is used for building and running the application.
- Enhanced documentation in `CLAUDE.md` and `install.md` to clarify the requirement for the vendored `tauri-cli` and the installation process.
- Improved the `dev:app` and `dev:wry` scripts to streamline the development workflow with the new CLI setup.
These changes enhance the development experience by ensuring the correct tooling is in place for building and running the application with CEF support.
- Commented out unused platform configurations for Ubuntu and Windows in the release.yml file to streamline the workflow.
- Reformatted the `needs` section in the `Publish draft release` and `Remove release and tag if build failed` jobs for better clarity and consistency.
These changes enhance the maintainability of the release workflow by improving its structure and readability.
The updater was wired client-side (prepareTauriConfig.js sets
plugins.updater.endpoints to
https://github.com/tinyhumansai/openhuman/releases/latest/download/latest.json
and embeds UPDATER_PUBLIC_KEY) but the manifest itself was never
generated after we moved off tauri-action — so installed apps would
fetch 404 and believe they were up to date forever.
Add scripts/release/publish-updater-manifest.sh which:
- Lists the release's assets via gh CLI
- Finds the updater bundles produced by createUpdaterArtifacts=true
(.app.tar.gz for macOS, .AppImage.tar.gz for Linux, -setup.nsis.zip
for Windows) for each of darwin-aarch64 / darwin-x86_64 /
linux-x86_64 / windows-x86_64
- Reads the matching .sig files (minisign base64 payloads)
- Composes latest.json per the Tauri v2 static-manifest schema with
version, pub_date, notes, and a platforms map
- Uploads it to the release via gh release upload --clobber
Wired as a new production-only job `publish-updater-manifest` that runs
after the build-desktop matrix. publish-release now waits on it, and
the asset-validation step requires /^latest\.json$/ so releases can't
ship without the manifest. cleanup-failed-release also tears down
if the manifest step fails.
Staging builds are deliberately skipped — they shouldn't poison the
public updater endpoint.
This commit updates the tauri-cef submodule to the latest commit, ensuring that the project is using the most recent changes and improvements from the upstream repository. This change is part of ongoing maintenance to keep dependencies up to date.
Move the vendored tauri-cef submodule pointer from d278ff5d1 (which sits
on `feat/cef-custom` — the wrong branch; .gitmodules tracks
`feat/cef-notification-intercept`) to 1b58f715f, the current tip of the
tracked branch.
Fixes macOS release builds, which were failing in the `cargo install
--locked --path vendor/tauri-cef/crates/tauri-cli` step with:
error[E0583]: file not found for module `notification`
--> src/main.rs:3:1
|
3 | mod notification;
| ^^^^^^^^^^^^^^^^^
tauri-bundler/build.rs previously copied only cef-helper/Cargo.toml and
src/main.rs into OUT_DIR before invoking a nested cargo build, but
cef-helper's main.rs contains `mod notification;` and the sibling
notification.rs was never copied. The fix on the fork (1b58f715f —
"fix(bundler): copy entire cef-helper/src/ tree, not just main.rs")
copies the whole src/ directory, which resolves the module.
Linux and the CI Docker image are unaffected because the bundler build
script short-circuits on non-apple-darwin targets; this only bites the
macOS release matrix.
The root .dockerignore excludes `app/` (it's sized for the openhuman-core
Dockerfile), which also excludes `app/src-tauri/vendor/tauri-cef`. The CI
image Dockerfile at .github/Dockerfile needs that path to compile the
CEF-aware tauri-cli, so the docker-ci-image workflow fails at the
`COPY app/src-tauri/vendor/tauri-cef /opt/tauri-cef` step.
BuildKit prefers `<dockerfile>.dockerignore` over the root one, so add a
dedicated .github/Dockerfile.dockerignore that keeps the vendored
submodule while still stripping target/, node_modules/, etc. Verified
locally: `docker build -f .github/Dockerfile .` reaches the verify step
with `cargo tauri --version` printing 2.10.1.
- Added a key to the entitlements file to allow audio input device access, ensuring proper functionality for applications utilizing audio features under the macOS Hardened Runtime.
- Added a step to generate a GitHub App token using the tibdex/github-app-token action, improving authentication for Docker image pushes.
- Updated the Docker push step to use the generated token instead of the default GITHUB_TOKEN, enhancing security and access control during the CI process.
- Revised the feature comparison table for OpenHuman and its competitors, improving descriptions and emphasizing key features such as self-learning capabilities and desktop integrations.
- Streamlined language for better readability and user understanding of OpenHuman's advantages.
- Ensured consistency in formatting and terminology throughout the document.
- Revised the feature comparison table for OpenHuman and its competitors, correcting the formatting and improving descriptions for clarity.
- Removed outdated language and streamlined content to better reflect current capabilities and advantages of OpenHuman.
- Ensured consistency in terminology and improved overall readability of the document.
- Revised the feature comparison table for OpenHuman and its competitors, improving descriptions and adding clarity to the open-source status, simplicity, memory capabilities, API complexity, extensibility, and desktop integrations.
- Streamlined language for better readability and user understanding of OpenHuman's advantages.
- Removed outdated sections to focus on current capabilities and improve overall document quality.
- Removed the legend section from the feature comparison table to streamline the content.
- Adjusted the feature comparison for OpenHuman and its competitors, focusing on clarity and relevance.
- Improved overall readability of the document to better convey OpenHuman's advantages.
- Revised the feature comparison table for OpenHuman and its competitors, improving descriptions of open-source status, cost, memory capabilities, API complexity, knowledge base strength, skills integration, and desktop features.
- Streamlined language for better readability and user understanding of OpenHuman's advantages.
- Corrected minor typographical errors to enhance overall document quality.
- Added a new section highlighting the UI-first approach, emphasizing a clean desktop experience and simplified onboarding process.
- Corrected typographical errors in the subscription model description for clarity.
- Streamlined language to improve overall readability and better convey the advantages of OpenHuman.
- Revised the feature comparison table for OpenHuman and its competitors, improving clarity on open-source status, cost, memory capabilities, API requirements, knowledge base strength, skills integration, and desktop features.
- Corrected minor typographical errors to enhance overall readability.
- Streamlined language to better reflect the current capabilities and advantages of OpenHuman.
- Revised the feature comparison table for OpenHuman and competitors, enhancing clarity on open-source status, cost, self-learning capabilities, API requirements, knowledge base strength, skills integration, and desktop features.
- Corrected minor typographical errors to improve overall readability.
- Streamlined language to better reflect the current capabilities and advantages of OpenHuman.
- Revised descriptions for key features to improve user understanding, including subscription model, memory capabilities, skills integration, and local AI functionalities.
- Consolidated and clarified language around desktop integration and user data management, emphasizing privacy and local processing.
- Removed outdated sections to streamline the document and focus on current capabilities.
- Temporarily disabled the steps for promoting Docker images from staging to release tags and appending Docker pull instructions to release notes in the GitHub Actions workflow. This change prevents potential errors during the release process while maintaining the structure for future implementation.lease
- Commented out the staging tag build and push step in the GitHub Actions release workflow, indicating that it should be uncommented when a staging tag is available.
- This change helps prevent errors during the release process while maintaining the structure for future implementation of the staging tag functionality.
- Commented out the Windows build notification section in the release workflow to prevent errors during the release process.
- Added a note indicating that the Windows build is currently disabled in the matrix, improving clarity for future updates.
- Added an "Early Beta" note to the README to inform users about the development status.
- Updated the download instructions in the README for clarity and added a script for global installation.
- Introduced a new BUILDING.md file detailing the steps to build and install OpenHuman from source or via stable releases.
- Added a placeholder install script to guide users on future installation options.
- Updated the signing workflow to sign non-main binaries (sidecars) before the main .app bundle, improving compliance with Apple notarization requirements.
- Added diagnostic output to display the main executable name and list contents of the app bundle for better visibility during the signing process.
- Improved comments for clarity on the new signing steps and their significance in the overall workflow.
- Updated the signing process to include signing of non-main binaries (sidecars) before the main .app bundle, improving compliance with Apple notarization requirements.
- Added diagnostic output to list contents of the app bundle and main executable for better visibility during the signing process.
- Improved comments for clarity on the new signing steps and their significance in the overall workflow.
- Adjusted the formatting of the name matching logic for the daemon executable in `common.rs` to enhance readability.
- Ensured consistency in the checks for the executable name across different operating systems, maintaining clarity in the codebase.
- Updated the build script to re-create the DMG with the stapled .app, ensuring compliance with Apple notarization requirements.
- Added notarization step for the DMG using xcrun notarytool, improving the overall security and integrity of the release process.
- Enhanced comments for clarity on the new notarization and stapling steps.
- Changed the default binary name from "openhuman" to "openhuman-core" in Cargo.toml and related scripts.
- Updated build and test workflows to reference the new binary name, ensuring consistency across the project.
- Adjusted paths and executable checks in the codebase to accommodate the renamed binary, improving clarity and maintainability.
- Updated the signing workflow to focus solely on signing the entire .app bundle with hardened runtime, eliminating unnecessary sidecar signing steps.
- Enhanced diagnostic output to list the contents of the app bundle before signing, improving visibility during the process.
- Improved comments for clarity on the new streamlined signing approach and its compliance with Apple notarization requirements.
- Updated the re-signing workflow to focus on signing sidecar binaries and frameworks with hardened runtime, ensuring compliance with Apple notarization requirements.
- Enhanced diagnostic output for better visibility during the signing process, including verification of sidecar binaries.
- Improved comments for clarity on the signing steps and their significance in the overall workflow.
- Bumped version to 0.49.30 in Cargo.lock to reflect changes.
- Updated the re-signing workflow to strip existing signatures before signing binaries and frameworks, ensuring compliance with Apple notarization requirements.
- Changed the signing approach to an inside-out method, signing nested code first and then the outer .app bundle.
- Enhanced diagnostic output for better visibility during the signing process.
- Updated comments for clarity on the new signing steps and their importance.
- Consolidated the re-signing of the entire .app bundle into a single command with the `--deep` option, improving efficiency and reliability.
- Removed redundant sidecar re-signing loops, simplifying the signing workflow.
- Enhanced diagnostic output to list contents of the app bundle, aiding in troubleshooting.
- Updated comments for clarity on the signing process and its requirements.
- Added steps to ensure the signing identity is available by creating and managing a keychain for certificate import.
- Implemented security commands to unlock the keychain and import the signing certificate, improving the reliability of the signing process.
- Cleaned up temporary certificate files after use to maintain a secure environment.
- Added a new step to locate the macOS .app bundle dynamically, improving reliability in finding the application during the release process.
- Updated subsequent steps to utilize the located .app path and bundle directory, ensuring correct signing and notarization of the application.
- Enhanced error handling to provide clearer feedback if the .app bundle cannot be found.
- Replaced direct Tauri invocations with a unified `callCoreRpc` function for skill management operations, enhancing code consistency and maintainability.
- Updated functions for listing, discovering, starting, stopping, and managing skill data to utilize the new RPC schema.
- Added new RPC handlers for skill discovery, listing, data reading, writing, enabling, disabling, and checking if a skill is enabled, expanding the skills management capabilities.
- Enhanced the SkillManifest struct to support serialization, improving data handling for skill manifests.
- Changed the workflow to create draft releases instead of published ones.
- Added a new job to publish the draft release after successful builds, enhancing the release process.
- Updated relevant steps to reflect the new draft status for releases.
- Introduced a new RPC schema to facilitate sending arbitrary RPC methods to running skills.
- Implemented the `handle_skills_rpc` function to process RPC requests, including skill ID, method name, and optional parameters.
- Updated the controller schemas to include the new RPC functionality, enhancing the skills management system.
- Introduced a new entitlements file for the sidecar to enhance security during code signing.
- Updated the GitHub Actions workflow to utilize the entitlements file in the signing process.
- Bumped OpenHuman version to 0.49.21 in Cargo.lock for dependency management.
- Configured tauri.conf.json to reference the new entitlements file for macOS builds.
- Added `openssl-sys` and `openssl-src` dependencies in Cargo.toml and Cargo.lock for enhanced cryptographic support.
- Updated `tauri.conf.json` to streamline build targets by removing the updater option, simplifying the configuration.
- Removed the Rust quality job from build.yml and added it to typecheck.yml, consolidating Rust-related checks into a single workflow.
- Streamlined the build process by eliminating unnecessary dependencies and steps in the build.yml file, focusing solely on building the Tauri app.
- Updated test files for Discord, GitHub, Google, and Twitter to improve code consistency by standardizing async function formatting and import statements.
- Enhanced readability by restructuring promise resolutions and waitFor assertions.
- Ensured uniformity in the handling of button click events across all OAuth provider tests.
- Reinstated macOS ARM64 build configurations in the release workflow for improved compatibility.
- Updated the version of the "OpenHuman" package in Cargo.lock to 0.49.18, ensuring consistency across the project.
- Refactored search directory handling in core_process.rs for better clarity and maintainability, particularly for macOS platforms.
- Added conditional compilation for macOS in various files to streamline platform-specific functionality.
- Introduced a new job in the release workflow to verify the presence and executability of the staged sidecar binary for all platforms.
- This enhancement ensures that the sidecar binary is correctly built and available before proceeding with the release process, improving reliability and reducing potential deployment issues.
- Removed the standalone core CLI binary build step from the release workflow to simplify the process.
- Introduced a new step to resolve the CLI artifact path, enhancing clarity and maintainability in the workflow.
- Updated environment variable handling for better integration with the build process, ensuring consistent artifact management.
- Changed the initialization of search_dirs from a vector to a mutable vector to allow for further modifications.
- This adjustment enhances the flexibility of the search directory management, particularly for non-macOS platforms.
- Bumped the version of the "openhuman" package in Cargo.lock and Cargo.toml to 0.49.17.
- Updated the version in app/package.json and app/src-tauri/Cargo.toml to reflect the new release.
- Adjusted the version in app/src-tauri/tauri.conf.json for consistency across the application.
- Commented out macOS ARM64 build configurations in the release workflow to streamline the process.
- Updated the environment variable for the backend URL from `VITE_BACKEND_URL` to `BASE_URL` for consistency.
- Ensured proper handling of Apple certificate and password secrets in the build environment, enhancing security and clarity.
- Improved the deployment target configuration for macOS builds, ensuring compatibility with the latest requirements.
- Upgraded Tauri CLI version from 2.9.6 to 2.10.0 in package.json and yarn.lock.
- Modified build commands in various workflow files to include the `--bin OpenHuman` argument, ensuring the correct binary is targeted during builds for macOS and Linux.
- Streamlined argument handling in the build workflows for consistency across platforms.
- Eliminated several functions related to thread selection, creation, deletion, and purging to simplify the Conversations component.
- Introduced a new variable to manage the selected thread's tool timeline, enhancing the component's state management.
- Improved code readability by reducing complexity and focusing on essential functionality.
