Releases: sayyid5416/pyinstaller
Releases · sayyid5416/pyinstaller
v1.6.1
What's Changed
- Add lfs option to inputs by @PrajwalVandana in #21
- Dynamic name of spec file artifact by @sayyid5416 in #23
New Contributors
- @PrajwalVandana made their first contribution in #21
Full Changelog: v1...v1.6.1
v1.6.0
What's Changed
- Bump versions for Node JS 20 by @aliencaocao in #18
- Added a new input: compression_level by @sayyid5416 in #19
Full Changelog: v1.5.1...v1.6.0
v1.5.1
v1.5.0
What's Changed
- [New Input]
clean_checkout
to handle cleaning after checkout by @aliencaocao in #14 - Fixes #11
Full Changelog: v1.4.0...v1.5.0
v1.4.0
New Input:
pyinstaller_ver
: Specific PyInstaller version you want to use (with proper signs, like==5.13.2
)
Added More Pyinstaller Options
What's Changed
Added support for more Pyinstaller options when using .py
file type: #9
--add-data <SRC;DEST or SRC:DEST>
,--add-binary <SRC;DEST or SRC:DEST>
,--collect-data <MODULENAME>
,--collect-all <MODULENAME>
Full Changelog: v1.2.1...v1.3.0
New Input & Improvements in workflow
What's changed
- [Added new input]
python_arch
to specify python architecture you want to use with python (default x64) (by @Young-Lord in #6) - Action workflow updated:
- Python would be installed earlier than any other steps.
- It would give flexibility to specify the python version, which is not available on runner machine ( Fixes #4 )
- Minor refactoring in scripts
- Readme improved
Full Changelog: v1.2.0...v1.2.1
Support for pyinstaller options
What's Changed
-
[NEW] Added support of pyinstaller options. #2
- Provide all options in "inputs.options: ".
- .py and .spec type of specs, both supports d/f types of options.
- Look at readme for the list of supported options.
-
README updated
- Information about new input, i.e "options".
- List of all supported options.
- List of all inputs and outputs with their description and default values.
Full Changelog: v1.1.0...v1.2.0
Support for .py files and Improvements
What's Changed
- [NEW] Now
.py
can also be used ininputs.spec
to create its executable. #1- Generated
.spec
will also be uploaded as artifact
- Generated
- Readme updated:
- Syntax highlighting in examples
- Removed pre-requisite instructions (generating
.spec
file is no longer required) - Added available-features section
Full Changelog: v1.0.2...v1.1.0
Improvements
Changelog
- Readme updated
- Better annotations for:
- When required inputs are missing
- Unsupported types of required inputs are passed
- If executable couldn't upload because of missing input for
upload_exe_with_name
- If upload fails because of low storage
- More info in summary:
- Python version which was used to generate exe
- Full Changelog: v1.0.1...v1.0.2