v1.5.10

Tag hotfix

v1.5.9

This patch release contains a fix for a critical bug affecting ontology updates and other minor improvements.

• fix a bug when parsing ontologies that contain foreign terms without names
• add links to profile website and phone
• display emails for remote profiles

v1.5.8

This release adds two important features for preventing bots from registering: a reCAPTCHA challenge on registration and a mechanism for administrators to restrict which email providers can be used for creating new accounts. To accommodate registries outside North America, we added support for internationalized domain names. Read more about this feature here.

We also addressed numerous bugs with the GO term recommendation feature. It is now more reliable and provides feedback to the user when terms cannot be recommended. It can detect cases where, for example, there are no GO terms available for a given model organism.

A few more issues were resolved:

• fix a bug when creating or revoking an access token from the admin section: the session was inadvertently set to read-only
• reduce memory usage when parsing the gene2go file by ignoring irrelevant lines
• fix display of non-grouping terms on the public profile: it now reflects the user selection instead of enumerating all the options
• limit which fields can be set when registering or creating a service account
• update yauaa to 7.24.0
• ignore TIER3 genes from GO terms with more than 50 associated genes; the term can be added but its genes won't

v1.5.7

This release addresses an issue with password reset and verification tokens that can be consumed by a third-party (i.e. an anti-virus software that analyses emails) by adding a minimal User-Agent-based challenge.

• implement a challenge for validating password reset and verification tokens
• redirect to the login page if a token was already used
• strip authentication token when logging errors in RemoteResourceService
• allow service accounts to be used as remote search user
• set the User-Agent header with rdp/{version} when communicating with partner registries
• use the production mode when bundling resources with Webpack
• update Spring Boot to 2.6.15
• update frontend dependencies

v1.5.6

• ensure that pending emails are sent on shutdown
• fix email configuration shadowing (regression from 1.5.5)
• rename "Organ Systems" to "Human Organ Systems"
• fix incorrect attribute name for taxon title message

v1.5.5

• customize your taxon appearance in messages.properties
• rename "Model Organism" to "Model System" to encompass biological systems that are not organisms
• update Spring Boot to 2.6.14
• update frontend dependencies
• restrict manual tiers to those enabled in the configuration

v1.5.4

• add support for MariaDB 10.6 LTS
• add testing support for MySQL 5.6
• fix JPA auditing for creation and modification timestamps
• add explicit default values for timestamps
• add User ID to the Google Analytics integration
• fix ordering of users lacking origin URL
• support ordering FAQ entries
• add a workaround when synonyms case change in ontologies

v1.5.3

• Fix counting of genes by tier in the public profile, the wrong column was referenced
• Always use configured API URLs to generate links to partner registries (see #342)
• Fix missing genes on public profiles from partner registries
• Add support for requesting access to anonymized results from partner registries (see #150)

v1.5.2

This release address a few minor issues.

• fix glitchy GO term tooltip placement, which was falling in a scroll box smaller than the tooltip size
• add missing admin.js bundle which prevented the "Refresh Messages" button to work properly

v1.5.1

This is a follow-up release to the 1.5.0 which address a few minor issues.

• better summary for ontology availability
• consistent capitalization of taxon common name
• Spring Boot and Springdoc update to 2.6.12 and 1.6.11 respectively
• fix moving inactive ontologies in the admin section
• numerous fixes suggested by SonarQube static analyzer
• use the user timezone for generating the date: field in OBO format, this field is not complying with ISO 8601, so it is the best assumption we can make in this case, we will eventually support the creation_date field in a future release #318
• add missing rollbackFor for checked exceptions