Bump version to 1.1.0 across version.py, README, manifest.json and
CHANGELOG. Update user guide with troubleshooting section covering the
SSL certificate reset workflow
- Pin qml_gui extras in setup.py to PyQt6>=6.7.0,<6.8.0, PyQt6-Qt6>=6.7.0,<6.8.0
and PyQt6-sip==13.10.2 for compatibility on both x86_64 and aarch64 architectures
- Add ARM64/aarch64 QML GUI installation instructions in README.md with the exact
pinned package versions required for correct operation on Apple Silicon and
Linux ARM64 systems
- Update README.md
- Bump version to 0.9.1 in all files
- Add detailed CHANGELOG for v0.9.1 with Linux AppImage build fixes
- Fix desktop notification: "Electrum" → "Pallectrum"
Fixes reproducible builds with ELECBUILD_COMMIT and improves
AppImage filename determinism.
- Add README-ELECTRUM.md preserving original Electrum documentation
- Update README.md with Pallectrum-specific information including features, installation, and configuration
- Maintain original Electrum structure while adapting content for Palladium blockchain
- this merges `contrib/deterministic-build/locale` and `electrum/locale`
- it is now once again possible have translations when running from a local git clone
- which was already possible in the past before crowdin removed their unauthenticated APIs
- see https://github.com/spesmilo/electrum/issues/9531
- however, the translations available are the often-old frozen strings from electrum-locale
- while previously one could just download the latest strings from crowdin
We don't actually need the development headers, instead using this as
a hack to be agnostic to the version scheme and pull in the latest.
related:
https://github.com/spesmilo/electrum/pull/8185https://github.com/spesmilo/electrum/pull/8320https://github.com/spesmilo/electrum/issues/8328#issuecomment-1518061250
debian 11 (stable) only has libsecp256k1-0
debian 12 (testing) atm only has libsecp256k1-1
ubuntu 23.04 only has libsecp256k1-1
I expect libsecp256k1-2 might soon get packaged too, now that upstream secp released v0.3.0.
So what do we tell users to install? well, turns out most distros have libsecp256k1-dev, which
just pulls in the latest secp.
Caveat: if there is a new secp release that actually gets packaged on a distro before we can react,
then this new instruction will not work.
note: unclear where to put these files... `contrib/build-wine/` and `contrib/osx/`
contain binary-building-related files. maybe we could have a `doc/` folder
if the need for more similar files arise.
atm there are these two, plus maybe `contrib/docker_notes.md`.
