Repository navigation
PyQtPass v0.5.0
Portable mode, translated store messages, QtPass's addGPGId setting, and
the first release on PyPI.
Portable mode
- A
pyqtpass.ininext to the program holds the settings instead of the
user's settings, like QtPass's portableqtpass.ini. Create an empty one
to run PyQtPass from a USB stick; the record of signed recipient lists
moves along with it.
Translations and settings
- The messages of the password store, the signed recipient lists, gpg and
the GnuPG home are translatable now; they were English in every language.
QtPass's translations fill in the ones the projects share, and Dutch has
all of them. - Settings, Git has "Automatically add .gpg-id files", like QtPass's
addGPGId. It is on by default, as before; turned off, setting the
recipients commits the re-encrypted passwords but leaves the.gpg-id
files out of git.
Release builds
- A workflow run no longer replaces the files of a draft release that already
has signatures. Re-pushing the release tag (say, to sign it) used to rebuild
the files after they were signed, so the.ascfiles no longer matched. - PyQtPass is published on PyPI:
pipx install pyqtpass. Publishing a
release uploads its sdist and wheel, with the translations, using trusted
publishing; every pull request builds and checks the package. - The package metadata names the supported Python versions and platforms,
and the README's picture and links work on PyPI too. The package carries
every licence text and names the logo's and font's licences as well. - Licensing follows the REUSE specification, like QtPass:
REUSE.toml
records the copyright and licence of every file (GPL-3.0-or-later; the
logo WTFPL; the Lato font OFL-1.1), with the licence texts inLICENSES/,
and CI checks it.
Downloads
Each file is listed in SHA256SUMS. A signed build provenance
attestation records the workflow run and commit that produced them:
gh attestation verify <file> --repo annejan/PyQtPass. Each file
also has the maintainer's GnuPG signature: gpg --verify <file>.asc.