This commit modifies the GitHub Actions release workflow to update an existing release (if one with the same tag exists) instead of creating a duplicate release when multiple releases are generated on the same day. The 'update: true' parameter has been added to the release step to achieve this behavior.
## Removal of the .deb
The stage for creating the Debian package has been removed, as it was generating errors. Now, only the `tar.gz` file containing the script is generated.
## Update Instructions
The release body explains two methods for updating:
1. **Direct Execution**: Download and run the specific version using the URL with the corresponding tag.
2. **Local Installation**: Download the `tar.gz` file, extract it, and run the script locally.
## Important Note and Support
- A note has been added to clarify that this is a **test release**.
- A subtle and professional reminder to donate has been included.
This commit introduces a new workflow that automates the release process for the Proxmox Enhanced Configuration Utility (PECU). The workflow:
- Triggers on pushes to the main branch and via manual dispatch.
- Generates a version number based on the current date.
- Packages the script into a tar.gz archive.
- Creates a Debian package (.deb) for easy installation.
- Publishes the artifacts in a GitHub release.
The fix ensures that the backup directory is correctly set to /root/backup-script, ensuring that the backup script saves and retrieves files from the intended location. This change resolves any potential issues with the backup path, ensuring the script functions as expected without errors related to file location.
- Added Intel iGPU detection.
- Implemented rollback function for GPU passthrough configuration.
- Added checks for backup directory and state file creation.
- Refined options flow, with enhancements to backup, restore, and modify functions for sources.list.
- Optimized detection and configuration functions for AMD, NVIDIA, and Intel devices.
Added a "Buy Me a Coffee" button to the README to allow users to support the project. The button is placed in a new "Support" section to keep it visible but not intrusive. This update aims to enhance user engagement and provide an easy way for supporters to contribute to the project's development.
