• v1.20.1 387297ef7b

    LDAP WebGUI v1.20.1
    All checks were successful
    Tests / pytest (Python 3.11) (push) Successful in 1m18s
    Tests / pytest (Python 3.12) (push) Successful in 1m17s
    Tests / shellcheck (install.sh, update.sh, bootstrap-ldap.sh, webupdate.sh) (push) Successful in 16s
    Release / Publish release (push) Successful in 3s
    Stable

    Lyra released this 2026-10-30 23:57:08 +01:00 | 30 commits to main since this release

    v1.20.0's code, re-published as the first release of a clean release
    repository: one commit per release, nothing but what ships. The
    development history lives in a separate repository. No code change.

    Changed

    • The release repository starts over at this release. Its main
      does not descend from the main of v1.20.0 and earlier, and the older
      tags and releases are not carried over.
    • Comments and documentation no longer point at development records
      that do not ship; where a pointer carried a reason, the reason is now
      written out in place.
    • The release workflow publishes a release only in the release
      repository; anywhere else a version tag is a marker and nothing is
      published.
    • /docs/ serves every operator document in docs/ — the repository
      carries no development records there any more.

    Upgrade notes

    • Every host that updates from a git clone has to re-clone once. The
      new main does not descend from the old one, so
      ldap-webgui-update --from-release (and the web update) refuses at
      step source with exit 1 and changes nothing. As root: move the old
      clone at /usr/local/src/ldap-webgui aside, git clone the release
      repository to the same path, re-create the clone-local credential
      helper if the old clone had one, chown -R root:root the new clone,
      then sudo ldap-webgui-update --from-release —
      docs/settings.md → Re-cloning the update clone.
    • For a private release repository, the access token in
      /etc/ldap-webgui/environment must be one that can read the new
      repository — a token bound to a single repository may have to be
      replaced before the re-clone.
    • An archive install is not affected; update it as before.
    • No nginx change.

    Update without git access: download the source tar.gz below, extract it, then run the update.sh it contains:
    sudo bash <extracted-dir>/update.sh --archive <tarball>

    Downloads