- Updated `release_metadata` function to support manual testing from the main branch without publishing.
- Added tests to verify behavior for manual main runs, tag releases, and restrictions on other branches.
- Modified workflow to conditionally publish images based on the event type and added logging for manual test results.
- Enhanced documentation to clarify manual testing procedures and workflow behavior.
- Added a GitHub Actions workflow for building and releasing the web application on version tag pushes.
- Introduced Python and JavaScript scripts for release metadata generation, validation, and smoke testing of the web release image.
- Updated .gitignore to include new artifacts and Python cache directories.
- Created Docker Compose configuration for deploying the web application with environment variable management.
- Enhanced documentation for deployment instructions and usage of the official web release image.
Deleted the web audit script and removed associated commands from package.json and CI workflow to streamline the project and eliminate unused functionality.
Verify Store packages against pinned Ed25519 keys and catalog metadata, persist installation provenance, and add Marketplace review and installation UI while preserving unsigned local packages.
Bundle standalone plugin authoring tools and add a six-platform CLI packaging workflow. Official key initialization and protected signing environment setup remain separate rollout steps.
- Added scripts to prepare and verify the Microsoft ConPTY package for Windows.
- Updated build workflows to include checks for bundled ConPTY in installers.
- Enhanced application support info to display ConPTY status and version.
- Modified the portable updater to handle ConPTY files during updates.
- Updated documentation to reflect changes in ConPTY usage and requirements.
- Introduced tests for ConPTY backend functionality to ensure reliability.
- Modified permissions for the Windows 7 build job to read contents instead of write.
- Added a new step to upload the Windows 7 build artifact after the build process.
- Created a new job to download the Windows 7 build artifact and upload it to the GitHub release.
- Changed the shell used for uploading the installer to bash for consistency.
- Introduced a new GitHub Action for building the Windows 7 x64 offline NSIS package.
- Updated workflows to include steps for building and uploading the Windows 7 installer.
- Refactored existing Windows 7 compatibility workflow to utilize the new build action, streamlining the build process.
- Enhanced build metadata capture and artifact management for Windows 7 builds.
- Added the `tauri/custom-protocol` feature flag to the Windows 7 compatibility workflow for both cargo probe and build steps, enhancing support for custom protocols in the application.
- Updated the WebView2 SDK version to 1.0.1020.30 and adjusted related SHA256 checksums for improved compatibility with Windows 7.
- Added a new function to install the legacy WebView2 loader, ensuring proper handling of loader replacements and validation.
- Enhanced the CI workflow to include steps for enabling Win7-only Cargo patches and verifying the availability of 7-Zip, streamlining the build process for Windows 7 compatibility.
- Introduced a new documentation file to record Windows 7 compatibility vendor patches, detailing necessary adjustments for specific dependencies.
- Introduced multiple PowerShell scripts to ensure compatibility of WebView2 with Windows 7, including runtime verification, installer content checks, and PE import audits.
- Added a workflow configuration for building and bundling the application specifically for Windows 7, ensuring proper handling of dependencies and runtime requirements.
- Implemented logic to prepare and validate the WebView2 fixed runtime and loader, enhancing the overall compatibility and user experience on Windows 7.
- Updated build configuration to include MSI as a bundle option for Windows targets.
- Modified asset naming to accommodate MSI files in the release process.
- Added verification for signed MSI targets in the release manifest.
- Introduced new configuration for Wix installer in Tauri settings, specifying upgrade code and install mode.
- Removed the direct reference to `TAURI_SIGNING_PRIVATE_KEY_PATH` in the environment variable setup for improved security.
- Cleaned up the signing command in the release workflow by eliminating unnecessary environment variable references.
- Ensured consistent handling of the Tauri signing key across both build workflows.
- Added `crypto` module to generate unique environment variable delimiters for Tauri signing keys.
- Updated the way the signing key is written to the environment, ensuring it is securely handled and properly formatted.
- Modified the signing command in the release workflow to remove the direct reference to the private key path, improving security.
- Changed `TAURI_SIGNING_PRIVATE_KEY` to `TAURI_SIGNING_PRIVATE_KEY_PATH` in build workflows to improve clarity.
- Updated the signing command in the release workflow to reflect the new environment variable name.
- Implemented a function to verify the presence of signed portable targets in the latest.json and r2-latest.json files.
- Enhanced error handling to ensure that missing signatures or URLs for required platforms are properly reported.
- Streamlined the process of checking for valid portable platform assets during the release workflow.
- Enhanced the installation process by creating a new virtual environment for Python dependencies, ensuring a clean setup.
- Added environment variables to disable pip version checks and input prompts.
- Upgraded pip, setuptools, and wheel, and specified exact versions for requests and requests-toolbelt.
- Included checks for installed packages to verify successful installation.
- Updated the release tag description to reflect the new version.
- Modified concurrency group to use workflow run ID for better tracking.
- Added conditional checks to ensure proper tag resolution for both manual and automatic triggers.
- Improved error messages for scenarios where release tags or assets are not found.
- Streamlined asset download and validation steps for better reliability.
- Introduced a new workflow to automate the building of the main snapshot for the NyaTerm application.
- The workflow includes steps for resolving the main branch SHA, building for multiple platforms (macOS, Linux, Windows), and collecting build artifacts.
- Added necessary environment variables and permissions for the workflow execution.
- Integrated Rust and Node.js setup, along with dependency installation for each platform.
- Added steps to prepare and clean the workspace before and after asset uploads, ensuring a fresh environment for each release.
- Implemented cleanup tasks to remove temporary files and directories, improving resource management and preventing potential conflicts in subsequent runs.
- Included the "tag_name" field in the Gitee release update requests to ensure proper tagging of releases.
- This change enhances the release management process by explicitly defining the tag associated with each release update.
- Updated the Gitee release workflow to create a Python virtual environment for dependency management.
- Installed `requests` and `requests-toolbelt` within the virtual environment to ensure isolation and compatibility.
- Modified the script to use the virtual environment's Python interpreter for executing the release creation process.
- Changed the runner for the Gitee release workflow to a self-hosted environment with specific labels for better resource management and compatibility.
- Added upload progress tracking for assets during Gitee release creation, improving user feedback.
- Updated error handling to provide clearer messages when Gitee tags are not found.
- Enhanced the workflow to include additional Python dependencies and improved asset upload configurations.
- Refactored release body generation to better handle asset upload statuses and provide informative messages in the release notes.
- Introduced a new GitHub Actions workflow to automate the publishing of releases to Gitee upon release events or manual dispatch.
- The workflow includes steps for validating Gitee configuration, waiting for Gitee mirror tags, downloading GitHub release assets, and creating or updating the Gitee release.
- Configurable options for asset uploads and error handling are provided through workflow inputs and environment variables.
- Removed the Homebrew tap update job from the build-release workflow.
- Added new workflows for publishing to AUR and Homebrew, triggered by the completion of the build-release workflow or manually via dispatch.
- Implemented version resolution and asset verification steps for both AUR and Homebrew publishing processes.
- Introduced a new job in the GitHub Actions workflow to update the Homebrew tap upon version tagging.
- Configured the job to trigger only for version tags without hyphens, ensuring proper version management.
- Utilized GitHub CLI to run the update workflow for the Homebrew tap, enhancing the release process.
Added a new job to publish release assets to Cloudflare R2, including downloading release assets, building the latest.json file, uploading installers, and verifying the uploaded latest.json.
Kang