Releases

Evergreen 3.17.0 available

The Evergreen Project is pleased to announce the release of version 3.17.0. 3.17.0 is a feature release that includes

Improvements to the Holdings Editor, including a new version of “working items” support and restoring the ability to unset fields
Improvements to the Patron Summary display, including displaying user preferences, number of overdue items across the patron’s family group, and more visibly displaying the privacy waiver status
Library Groups can now be taken into account when configuring circulation and hold policies
Circulation and hold policies can now be cloned
Email receipts can now be sent from the Items Out, Renew Items, and Checkin interfaces
Patrons can now set a hold expiration date when placing holds through the public catalog
The ability to populate Item Buckets by importing from CSV files
New methods for allowing patrons to set fine-grained opt-ins to notifications
Many grids in the staff interface now have case-insensitive filtering
ChiliFresh is now supported as a cover image provider
StackMap integrations can now be more easily enabled in the public catalog
Support for installation on Debian 13 “Trixie”
Support for PostgreSQL 18
Various accessibility improvements

Evergreen 3.17.0 is available for download.

Evergreen 3.17-beta3 available

The third beta release of Evergreen 3.17 is now available. As compared to the first beta of 3.17, this release includes a significant upgrade of the Angular framework used by the staff interface. While this change is an internals-and-plumbing change that should not result in any visible changes to the staff interface, it does have the potential to cause breakage. Consequently, beta testers are strongly encouraged to thoroughly test all staff interfaces.

This release also contains the following bugfixes since the first beta:

Fix crash that can occur when Quipu eRENEW attempts to update certain patron records. (Bug 2143938)
Fixes issue where recall holds on a items with a monograph part fail to be targeted (Bug 2130052)
Fixes issue where force holds on a items with a monograph part fail to be targeted (Bug 1838069)
Fixes F-type targeting issue that alternates between targeting and not targeting an item. (Bug 2131948)
Prevent simplistic scraper bots from wasting resources. (Bug 2113979)
Fixes bug where the age hold protect value was not included in CSV exports from the Item Table. (Bug 2146564)
Fix erroneous number on my list count. (Bug 2138265)
Fixes a security issue with certain database query generation methods (Bug 2147196)
Fixes a typo in the output of the /openils/bin/api_ctl program. (Bug 2147136)
Adds missing cancel if not filled by alert dialog in staff client. (Bug 2147225)
Removes references to the “tundra” CSS class in the TPAC/BOOPAC (Bug 2056771)
Fixes issue where when a staff member places a hold for a patron via the Traditional (embedded) Catalog, the “No configured email address” warning would show up inappropriately. (Bug 2148326)
Fixes issue where some invoices charge twice when calculating warning and stop percentages. (Bug 2088125)
Restores automatic focus on the barcode input after patron logout in the Angular self-check. (Bug 2127936)
Prevents duplicate patron self-registration submissions by double click. (Bug 1913626)

The beta release is available for download. The release candidate is scheduled for May 6, 2026 and general release is scheduled for May 13, 2026.

Evergreen security release: 3.14.12, 3.15.12, 3.16.6, 3.17-beta2

The Evergreen Project has issued the following security releases;

3.14.12
3.15.12
3.16.6
3.17-beta2

These fix vulnerabilities that allow remote exfiltration of the contents of the database and the remote execution of arbitrary SQL and stored procedures in the Evergreen database.

These releases are available on the downloads page.

We strongly recommend immediate installation of this security release.

The two security bugs fixed in this release are:

These bugs will be made publicly visible over the next few days.

If you are running a version of Evergreen earlier than 3.14, please consult with your service provider or review the fixes in Git to update your system.

We would like to thank the individual who reported bug 2147196.