Broadleaf Microservices
  • v1.0.0-latest-prod

Upgrade to 1.7.6-GA

Note

Microservices release 1.7.6-GA is congruent with:

  • Frontend Libraries

    • AdminWeb 1.8.7-rc1.0

    • CommerceSDK 1.4.6-rc1.0

    • Payment JS SDK 1.1.5-rc1.0

    • Auth SDK 1.4.2

  • Frontend Starters

    • AdminStarter 1.8.5-rc1.0

    • NextJS Starter 1.4.5-rc1.0

Requirements

  • JDK 11 is now required for the Broadleaf 1.7.0-GA release train, and beyond.

Bug Fixes

  • This is a sparse release from 1.7.5-GA with a couple of bug fixes

  • Fixes an issue with Camel Cluster Service dependency versions that was causing stability issues with cluster services used in Broadleaf. This primarily impacted durable messaging fallback functionality and the ScheduledJobs service. Messages would still send correctly, but in the case of a broker outage, the fallback system would not pick up the previously failed messages. Also, since the ScheduledJobService was not functioning properly, scheduled jobs would not execute, including scheduled deployments. This will have been a problem since 1.7.3-GA for those that adopted that release (or beyond) and also accepted the latest Spring Boot dependencies that were included by default.

  • Fixes an issue with caching where incorrect results could be returned from a cache. Cache is used in several places in the framework, including in catalog, offers, auth, and other scenarios. It was possible, on occasion, for a mismatch to occur between what was requested and what was matched in cache. This would only have effected adopters of 1.7.5-GA, and not previous releases.

Helm Chart Updates

Starting with 1.7, we have begun publishing common base charts to a private helm repository. In order to pull in and use these charts, you will need to authenticate (i.e. helm repo add broadleaf https://repository.broadleafcommerce.com/repository/helm-private/ --username $BLC_REGISTRY_USER --password $BLC_REGISTRY_PASSWORD ) using the same credentials that were sent to you (these are the same credentials that allow you to build and run the microservice applications).

See the following for more details: