Releases: indygreg/PyOxidizer
Apple Codesign 0.14.0
This is the first GitHub release for apple-codesign / rcodesign
with pre-built executables!
The macOS binary is self-signed using the new remote signing feature. The signing was initiated on GitHub Actions (https://github.com/indygreg/PyOxidizer/runs/6152561538?check_suite_focus=true) and signing was performed from the maintainer's Windows machine using a YubiKey.
The permalink for documentation for this release is https://pyoxidizer.readthedocs.io/en/apple-codesign-0.14.0/apple_codesign.html
- Fixed a bug where symlinks weren't been written in notarization zip file
files properly. This prevented bundles containing symlinks from notarizing
correctly. - The filename used in notarization uploads is now normalized to avoid
rejection due to spaces and colons. - Support for remote signing. The feature is documented extensively in the
Sphinx documentation. Essentially, 2 independent machines communicate with
each other with end-to-end encrypted messages via a websocket bridged through
a central server. Signing requests are sent to a remote machine which is in
possession of the signing key. Signatures are made on the remote machine and
transmitted back to the originating machine. Remote signing enables signing
to be performed more securely by facilitating signing without having to give
the initiating machine access to the signing key. - Default log output format has changed. Lines are no longer prefixed with the
time, log level, or logging module by default. A-v/--verbose
global flag
has been added to increase the verbosity of logging. This can restore the
printing of the prefixes. This crate uses
env_logger <https://crates.io/crates/env_logger>
_, so it is possible
to customize default behavior via environment variables. - The possible values for the
--code-signature-flags
are now advertised in
help output. - Written Mach-O files should now always have their filesystem permissions
preserved. Before, we may not have preserved file permissions in all code
paths writing Mach-O files. - A new
keychain-print-certificates
command can be used to print
certificates available in macOS keychains. - Initial support for using macOS keychain certificates for code signing.
Previously, we required that certificates be exported from keychain in
order to sign. We now support signing using SecurityFramework APIs so
keys don't have to leave the keychain. Due to a limitation in the Rust
bindings to SecurityFramework, decryption using keychain keys is not
supported. So the public key agreement method of remote code signing
will not yet work with keychain-based keys. The new--keychain-domain
and--keychain-fingerprint
arguments can be used to specify how to
search for and use keychain hosted keys.
PyOxidizer 0.20.0
PyOxidizer 0.18.0
Release notes at https://pyoxidizer.readthedocs.io/en/pyoxidizer-0.18.0/pyoxidizer_history.html#version-0-18-0.
We would like to thank @davidhewitt and the other maintainers of the PyO3 project. This PyOxidizer release, its switch to PyO3, and the benefits that switch provides - and will provide - would not be possible without your willingness to support PyOxidizer's somewhat esoteric use cases. For your patience and support, we thank you.
PyOxidizer 0.17.0
PyOxidizer 0.16.0
See the release notes at https://pyoxidizer.readthedocs.io/en/stable/pyoxidizer_history.html#version-0-16-0
The Python wheels have a 0.16.2
version component because the initial build of the 0.16.0
and 0.16.1
macOS wheels was buggy due to the pyoxidizer
file not being executable and therefore not being installed by pip
. There were no functional changes between 0.16.0
and 0.16.2
.
PyOxidizer 0.15.0
PyOxidizer 0.14.1
See release notes at https://pyoxidizer.readthedocs.io/en/stable/pyoxidizer_history.html#version-history.
Release artifacts/installers coming shortly.
PyOxidizer 0.13.2
pyoxidizer/0.13.2 releasebot: release-version-change pyoxidizer 0.13.2-pre -> 0.13.2
PyOxidizer 0.13.0
pyoxidizer/0.13.0 release: update pyoxidizer from version 0.13.0-pre to 0.13.0
0.7.0
See https://gregoryszorc.com/blog/2020/04/09/pyoxidizer-0.7/ for the blog post accompanying this release.
The over-arching theme of this release was focusing on improving PyOxidizer's compatibility with various packages. It has done so by:
- Supporting loading extension modules from standalone files.
- Reusing pre-compiled extension modules in Python binary wheels
- Better support for loading Python resources from the filesystem
- Improved handling of Python package resource files
- Initial support for package distribution metadata (
.dist-info
and.egg-info
directories) - And lots more. See the full changelog at https://pyoxidizer.readthedocs.io/en/stable/history.html