Feature/27 preparations for publishing #28
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Translated the README.md content from Japanese to English for broader accessibility. - Moved the 'Privacy' section under 'Features' for better organization. - Removed detailed setup instructions to streamline the README. - Added a screenshot to visually represent the application. Additionally, added a new screenshot image (screenshot.png) under the public directory.
- Updated `rusqlite` dependency to version 0.32.1 in Cargo.toml. - Removed `ApiKey` struct from `database.rs` and replaced its usage with a direct `String` parameter for API key handling. - Modified the `chat_gpt` and `get_available_models` commands to accept API key as a parameter rather than using Tauri state. - Simplified API key retrieval in `App.vue` by introducing `getApiKey` method and refactoring related methods to handle API interactions. - Enhanced error handling across API interaction methods in `App.vue` for robustness. - Removed unnecessary state management for `ApiKey` in `lib.rs`. - Improved code readability and maintainability by adding helper methods in `App.vue` for API operations.
- Updated all instances of "Chauri" to "Cuuri" in project files including README.md, package.json, Cargo.toml, and configuration files. - Adjusted file paths and identifiers to reflect the new project name. - Ensured consistency across the codebase with the new name.
- Replaced the manual app build step with Tauri GitHub Action in the workflow. - Configured the action to use the GITHUB_TOKEN and matrix arguments for more flexible builds. chore: update screenshot image in the public folder - Updated the screenshot.png file to reflect the latest UI changes.
- Added a new section on how to customize Cuuri data storage. - Explained the location and purpose of files in `$HOME/.cuuri`. - Provided details about `chat.db` for chat history and `config.toml` for configuration. - Included instructions for setting `default_model` and `openai_api_key` in `config.toml`.
- Updated existing icon files in `src-tauri/icons` with new versions. - Added new Android launcher icons for various densities (hdpi, mdpi, xhdpi, xxhdpi, xxxhdpi) including `ic_launcher`, `ic_launcher_foreground`, and `ic_launcher_round`. - Introduced new iOS AppIcon assets for different sizes and scales (20x20, 29x29, 40x40, 60x60, 76x76, 83.5x83.5, 512@2x). - Added a new export image `export_hvnp2g.png`. - Updated platform-specific icon files: `icon.icns` and `icon.ico`. These changes ensure compatibility with various platforms and improve the visual quality of the app's icons.
- Updated various PNG icon assets across multiple resolutions and platforms including Android, iOS, and desktop. - Modified existing icons such as 128x128, 32x32, and several specific app icons for both Android and iOS platforms. - Added a new SVG file `export_hvnp2g.svg` created with Inkscape, which includes vector graphics for scalability. - Revised binary icon files (`icon.icns`, `icon.ico`, `icon.png`) to reflect new design updates.
- Updated multiple PNG icon assets across various sizes and resolutions in the `src-tauri/icons` directory to new versions. - Modified SVG file `export_hvnp2g.svg` to adjust specific path and style attributes. - Updated icon sets for Android, iOS, and general application use, including `icon.icns`, `icon.ico`, `icon.png`, and several iOS-specific app icons. - These changes likely improve visual quality and ensure better compatibility with various devices and platforms.
- Changed the `productName` in `src-tauri/tauri.conf.json` from "cuuri" to "Cuuri" to follow proper capitalization standards. - This change ensures consistent branding and presentation of the application name across all platforms.
- Added a centered logo image at the top of the README for better visual appeal. - Included a centered `<h1>` title under the logo to enhance the presentation and branding of the "Cuuri" application. - These updates improve the README's layout and make it more engaging for viewers.
- Updated the workflow to trigger on all branch pushes, excluding `release`. - Introduced a new `setup` job to configure Node.js and Rust environments, leveraging caching for Node.js modules to optimize build times. - Modified the `build` job to depend on the `setup` job, ensuring environments are prepared before building. - Consolidated installation steps and enhanced caching: - Removed redundant Node.js setup and dependency installation in the `build` job. - Added caching logic to restore Node.js modules conditionally. - Updated the `build` job to utilize the `tauri-apps/tauri-action` for building the Tauri app. - Ensured the `release` job is contingent on the `build` job and aligns with the `release` branch, using `tauri-action` to draft GitHub Releases. These changes streamline the CI/CD process, improving efficiency and reliability for multi-platform builds and releases.
- Deleted `actions.yml` to separate build and release workflows for better clarity and maintainability. - Introduced `build-common.yml` to define common setup steps for node, Rust, and dependencies across platforms. - Added `build.yml` for handling build processes across different platforms with matrix strategy. - Created `release.yml` specifically for release tasks, ensuring builds are conducted and releases are drafted on designated branches. - These changes enhance modularity and reusability of the workflow configurations.
- Removed the redundant `actions/checkout@v4` step from `build-common.yml` to prevent unnecessary duplication. - Added `actions/checkout@v4` step at the start of `build.yml` and `release.yml` to ensure the repository code is checked out before executing subsequent steps. - This update corrects the workflow sequence to ensure proper access to the codebase during the build and release processes.
- Added a `call-common-workflow` job in both `build.yml` and `release.yml` to utilize the `build-common.yml` for setup tasks, enhancing modularity. - Removed redundant `checkout` steps from `build.yml` and placed them in `build-common.yml` to adhere to DRY (Don't Repeat Yourself) principles. - This refactor ensures consistent setup across build and release processes, leveraging the shared `build-common.yml` workflow for setup tasks.
- Added `needs: call-common-workflow` to both the `build` and `release` jobs in `build.yml` and `release.yml` respectively. - This ensures that the `build` and `release` jobs will only run after the common setup steps have been completed successfully. - These changes enhance the reliability of the workflows by properly sequencing the jobs.
…I workflows" This reverts commit da00752.
…ciples" This reverts commit 2990999.
This reverts commit 9700446.
This reverts commit c702af5.
This reverts commit 5b47337.
- Deleted the 'branches-ignore' rule for the 'release' branch in the actions.yml. - This change allows the build job to be triggered on pushes to the release branch.
- Introduced concurrency control to the `test-build-only.yml` workflow to prevent concurrent runs on the same branch or tag. - The `concurrency` feature uses the format `workflow-ref`, ensuring that only one run is active per branch or tag at a time. - Enabled `cancel-in-progress` to automatically cancel any in-progress runs of the same workflow when a new run is triggered, optimizing resource usage and reducing potential conflicts.
…ents - Modified the `publish` workflow configuration to trigger on `pull_request` events specifically targeting the `release` branch. - Set the workflow to activate on `opened`, `synchronize`, and `reopened` pull request event types. - This update ensures that the workflow runs only when a pull request is made to the `release` branch, improving the release process by reducing unnecessary builds.
|
close #27 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.