Repository navigation
v0.21.0 - Momentum: Improved Speed
packer Update [0.21.0]
This release enhances project configuration documentation, introduces AI suggestions control, supports streaming to GitHub assets and GoFile uploads, Introduces threading for smoother output, reorganizes setup process, simplifies temporary file handling, and rectifies various template and waiting logic issues.
Installation
Available via:
- GitHub: GitHub Releases
- Third-party website (GoFile): Archive (click the download button).
Binary Downloads
When downloading, please choose the correct build for your operating system:
| File Name | Platform | Description |
|---|---|---|
packer |
Linux/macOS | Executable for Unix-based systems. |
packer.exe |
Windows | Executable for Windows systems. |
To install:
- GitHub:
Download the appropriate binary for your system from the Releases page. - Third-party website (GoFile):
Head to the website Archive and download the specific arhive with the appropriate version.
After installing, continue following instructions via the README.
Changes in 0.21.0
Added
- [16f98aa] Various documentation updates to reflect new features and options in the project configuration.
- [16f98aa]
--ai-suggestionsparameter to theCLIfor disabling AI suggestions in thechangecommand. - [7b4af00] Optional file path parameter for text editor input function to use existing files, if None it wil act as before and create it's own temporary file.
- [d3a7d56] Streaming to GitHub assets and GoFile uploads.
- [f15bb84] Option to skip AI suggestions via keyboard interrupts (ctrl+c).
- [f15bb84]
Packerclass now creates a project specific cache dir to allow running multiple instances. - [feff634] Threading for smooth output to allow the program to run at near full speed instead of creating artificial slow down for looks, also dynamic speed is possible with this approach.
Changed
- [16f98aa] The latest parameters of
Packer, like,check_todo,todo_rel_path,list_start_identifier, andlist_end_identifierhave been moved toProjectclass in config.py, Packer just references them from there. This change was made to be able to have settings validation. - [16f98aa] TODO in
setup.pyto have sections for all entries, like before committing, before release and so on. This will help in organizing the setup process and ensuring that all necessary steps are completed before committing or releasing the package, Packer also checks these by default. - [7b4af00]
mainfunction inchange.pynow acceptstext_editorandwait_flagparameters. - [7b4af00]
input_via_text_editorfunction inconfig.pynow delegates to the module-level function with additional parameters. - [70bd993] Simplified and sped up the logic for waiting the buffer to be processed and emptied.
- [3f21cd7] The
format_sizefunction to handle negative size values.
Fixed
- [16f98aa] Release notes template to use program name variable instead of hardcoded 'packer' and 'packer.exe'.
- [7b4af00] Proper handling of temporary files in text editor input, ensuring cleanup when not using existing files.
- [7b4af00] Correct passing of wait flag to text editor commands when specified.
- [3923266] Changed the smooth output threading
Queueobject to be one of the queue modules instead of Multiprocessing. - [6a29654]
"versions size"to"version size"key of the metadata.json to actually check and compare to last version's size. - [7120d68] Waiting for the printing to finish before prompting for anything through stdin.
- [b392cf1] Added a wait condition before streaming compile or bundling commands via
_Popen. - [b392cf1] The upload_asset_from_memory method now uses
path.getsize(file_path)instead ofpath.getsize(f)to get file size in the _upload_github_asset function.
Tips
If you prefer to build from source via GitHub, you can clone the repository using:
git clone https://github.com/EMILIO888real/Packer --depth 1
Using --depth 1 creates a "shallow clone," which only downloads the latest commit, saving you significant time and storage space compared to a full repository clone.
While downloading the pre-compiled binaries (like packer or packer.exe) is usually the fastest way to get started, cloning the repository allows you to easily pull future updates with git pull as they are released.
Verification
To ensure the integrity of the downloaded files, you can verify their SHA256 checksums.
How to verify:
- Windows (PowerShell):
Open PowerShell and run the following command:
Get-FileHash .\packer.exe -Algorithm SHA256
- Linux/macOS (Terminal):
Open your terminal and run:
sha256sum packer
Compare the resulting hash with the one provided in the GitHub release assets list to ensure it matches.