Commits on Jun 21, 2023

1. Pre-release Themis 0.15.0 (#1011) …

   * Fix rust issues (pin log, run bindgen) (#1005)
   
   * rust: Pin log version to =0.4.18
   
   The 0.4.19 requires rustc 1.60, but currently we support 1.58.
   Pinning it is not a big deal since it's development dependecy for
   tests and examples.
   
   * rust: Regenerate and update lib.rs
   
   bindgen was updated again and changed something which resulted in
   new output (seems like some internal constants are removed).
   
   * Pythemis: introduce `pyproject.toml` (#1006)
   
   * pythemis: Add pyproject.toml
   
   Since setup.py is deprecated, let's try moving to the pyproject.toml
   and configuring it with the same data as in setup.py.
   
   Use setuptools as a backend for no particular reasons ¯\_(ツ)_/¯,
   just because the name is familiar and we have no reasons to not use
   it or use something else.
   
   Keep the old setup.py for backward compatibility so old systems can
   try to build the package.
   
   For now, keep 0.14.0, we will bump the version in another PR.
   
   * makefile: Use pyproject.toml for installing pythemis
   
   According to this [1] article, the correct command is
   
       pip install .
   
   in the project's root. Let's try that. Also, the other option is
   
       python -m build --wheel
   
   which builds the package but doesn't install it. We can provide
   something like `pythemis_build` for it for example.
   
   [1]: https://godatadriven.com/blog/a-practical-guide-to-setuptools-and-pyproject-toml/
   
   * pythemis: Update classifiers to Python3.6+
   
   With many hours and docker containers I tested that themis actually
   works up to python 3.4. The other versions require some changes in
   makefile so they are more like "grey area".
   
   However, python3.5 is deprecated and it produces warning like
   "DEPRECATION: Python 3.5 reached the end of its life on..." so many
   libraries don't support it. Instead they start with 3.6 which will
   do as well, I guess.
   
   Though, actually python3.6 is also deprecated [1]. The same will be
   true for python3.7 in a couple of days (Jun 27 2023), so the question
   is, should we declare support of these versions?
   
   [1]: https://devguide.python.org/versions/
   
   * pythemis: Extend range of supported py versions
   
   * Update changelog
   
   * Run and pin bindgen (#1008)
   
   * rust-themis: Update bindgen
   
   It updated and broke something again 🤦
   
   * rust-themis: Pin bindgen version
   
   It is pretty unstable with its frequent releases, so let's pin it.
   
   * Update changelog
   
   * Bump wrapper versions to 0.15.0 (#1007)
   
   * changelog: Add 0.15.0 summary
   
   * themis-core: Update version
   
   * pythemis: Update version
   
   * pythemis: Fix 8-year old typo in AUTHORS :)
   
   * rbthemis: Update version
   
   * jsthemis: Update versions
   
   * wasm-themis: Update versions
   
   * android-themis: Update version
   
   * rust-themis: Update versions
   
   * react-native-themis: Update versions
   
   * pythemis: https in AUTHORS
   
   Co-authored-by: vixentael <[email protected]>
   
   * rust-themis: Update bench versions
   
   Somehow missed that.
   
   * changelog: Forgot to mention rust 1.58
   
   * changelog: Mention the new iteration count
   
   ---------
   
   Co-authored-by: vixentael <[email protected]>
   
   * Bump embedded BoringSSL (#1004)
   
   * Bump BoringSSL and fix makefile
   
   This is not the latest BoringSSL version yet, because there are
   a couple of fixes. So, treat it as the first. Here we also fix
   our makefile because the BoringSSL team fixed bug with the strange
   behaviour of absolute path to symbols.txt [1].
   
   [1]: https://boringssl.googlesource.com/boringssl/+/8c75ed046f799f1d8b805036b1dea9c5ec0a0fb5%5E%21/#F0
   
   * Bump BoringSSL and fix opaque EVP
   
   As OpenSSL, BoringSSL made many types opaque, so it will require
   updating some of the code to not use fields.
   
   * Bump BoringSSL again and fix RSA
   
   The same issue - RSA type became opaque, so we need to use accessors
   similar to what Openssl had.
   
   * Bump BoringSSL once more
   
   This is (hoperfully) the last bump. This time without issues but
   we will see what CI says.
   
   * Make bignum_to_bytes accept const bignum*
   
   It will prevent some of the warnings. This function doesn't mutate
   bignum anyway.
   
   * Update changelog
   
   * boringssl: Bump once again
   
   * msys2: Update hashes temporarily
   
   This are test values because we will move the tag. But for now,
   let's just test it.
   
   * phpthemis: Update version for the sake of testing
   
   They will fail probably, but just out of curiosity let's try to run
   the tests.
   
   * Update date of the release
   
   Solstice!
   
   ---------
   
   Co-authored-by: vixentael <[email protected]>

   

   G1gg1L3s and vixentael authored Jun 21, 2023
   Configuration menu

   • View commit details
   • Copy full SHA for 22d8443
   • Browse repository at this point

   Copy the full SHA

   22d8443 View commit details

   Browse the repository at this point in the history

2. msys2: Update checksums (#1012) …

   It's the egg-chicken problem: we can update those hashes only
   after the release. But then, the release tag will not point to
   the updated hashes.

   

   G1gg1L3s authored Jun 21, 2023
   Configuration menu

   • View commit details
   • Copy full SHA for d925c3b
   • Browse repository at this point

   Copy the full SHA

   d925c3b View commit details

   Browse the repository at this point in the history