Announcing Hyrax 5.1.0

14 views
Skip to first unread message

nhom...@gmail.com

unread,
Apr 23, 2025, 4:37:17 PMApr 23
to samvera-tech

Hello all,


We are pleased to announce the release of Hyrax 5.1.0. This release includes the following significant changes and features:

  • Upgrade dependencies to support Ruby 3.3 and Rails 7.2


Additionally, this release now offers Fedora 6 as a supported and tested persistence adapter, with improved migration tooling forthcoming. If you’d like to see this version of Hyrax in action using Fedora 6, we have a test instance of Nurax available at: https://f6.nurax.samvera.org/. If you’d like admin permissions, please contact me.


Please be aware that the base image for Hyrax Docker images has changed from Alpine Linux to Debian Linux.

 

Full release notes are available at: https://github.com/samvera/hyrax/releases/tag/hyrax-v5.1.0


This release has been tested by users during the past two Hyrax Maintenance Working Group sprints, and the following issues are noted, in addition to other unresolved issues in the backlog:

  • For a "Wings" based work (i.e. Valkyrie models on Fedora 4), changes to file order in the File Manager are not reflected in the manifest and so the viewer does not reflect the changed order. The underlying issue, as documented in #7012, is an incomplete handling of the Fedora 4 members container by the ActiveFedoraConverter class handling the dynamic conversion between Valkyrie and ActiveFedora. It does work as expected for older ActiveFedora based works, as well as Valkyrie resources on Postgres and Fedora 6.

  • For a "Wings" based work (i.e. Valkyrie models on Fedora 4), uploading a new version of a FileSet does not change the thumbnail or version displayed in the viewer. This is potentially related to #6998. It does work as expected for older ActiveFedora based works, as well as Valkyrie resources on Postgres and Fedora 6.

  • The Rails 7.2 default autoloading behaviors are not compatible with the preexisting patterns that the Hyrax codebase contains for including classes. Fixing this would require a lot of rearranging and refactoring, so the consensus for achieving a timely release of Hyrax 5.1 is to override the add_autoload_paths_to_load_path default back to true in applications generated from the install template. Example refactoring for the more comprehensive approach can be seen in #7014.

  • Viewing “Your Collections” and “All Collections” in the Dashboard is slow. This is due to unoptimized loading of the list of collections using fedora queries. A fix using Solr is in progress, but until then expect the collections dashboard to be slow if a significant number of collections exist.: #7073.


Thank you to everyone who contributed to this release through development and testing work:

  • Daniel Pierce 

  • Randall Floyd

  • Julie Hardesty

  • Rob Kaufman

  • Kiah Stroud

  • Kirk Wang

  • David Moles

  • Greg Wiedeman

  • Rebekah Kati

  • Christine Peterson

  • Johannes Frenzel

  • Randy Kuehn

  • Patrick Schilf

  • Tracy McCormick



On behalf of the Hyrax Maintenance Working Group,


Nick Homenda

Hyrax Product Owner

Reply all
Reply to author
Forward
0 new messages