Liferay Portal 7.4 GA50 and Liferay Commerce 4.0 GA50 Release

We are pleased to announce the release of Liferay Portal 7.4 GA50 and Liferay Commerce 4.0 GA50!


Download options

Liferay Portal and Liferay Commerce share the same Bundle and Docker image.  To get started using either Liferay Portal or Liferay Commerce, choose the best download option suited for your environment below.

Docker image

To use Liferay Portal 7.4 GA50:

docker run -it -p 8080:8080 liferay/portal:

For more information on using the official Liferay docker image see the liferay/portal repo on Docker Hub.

Bundles and other download options

If you are used to binary releases, you can find the Liferay Portal 7.4 GA50 and Liferay Commerce 4.0 GA50 release on the download page.  If you need additional files (for example, the source code, or dependency libraries), visit the release page.

Dependency Management

For development using the Liferay Platform, update Liferay Workspace to use the  latest dependencies, by adding the following line to the build.gradle file:

dependencies {
	compileOnly group: "com.liferay.portal", name: "release.portal.api"

All portal dependencies are now defined with a single declaration. When using an IDE such as Eclipse or IntelliJ all apis are immediately available in autocomplete for immediate use.  

By setting a product info key property it will be possible to update all dependencies to a new version by updating the liferay.workspace.product property in the liferay workspace projects file:

liferay.workspace.product = portal-7.4-ga50

When using an IDE such as Eclipse or IntelliJ all apis are immediately available in autocomplete for immediate use.



Publication user is able to see the workflow status of entities when reviewing changes.

This feature was created so that the Workflow approval process can be used for changes in a Publication.

This is needed by users and customers that utilize Workflow processes while in a Publication and wish to prevent publishing of a Publication that has unapproved Workflow items.

Users will now be prevented from publishing a Publication that contains unapproved Workflow changes, where an “unapproved” change is one with a Workflow status that isn’t “Approved”. To facilitate this, Users will now be able to easily see the Workflow status of individual changes to Workflow-enabled entities in a Publication with the help of a newly added column on the Review Changes page.

This feature is aimed at Users. It can be used by enabling Workflow in a Publication. Once enabled, the features added in this ticket do not require any further configuration to use.

It allows Users to have Workflow approval processes within a Publication and prevents accidental publishing of a Publication that still has unapproved changes by requiring that all changes to workflow-enabled entities be approved. This enables a more granular way for individual changes to be approved by a reviewer and creates a fail-safe against premature publishing.


All documentation for Liferay Portal and Liferay Commerce can now be found on our documentation site:  For more information on upgrading to Liferay Portal 7.4 GA50 see refer to the Upgrade Overview.

Compatibility Matrix

Liferay's general policy is to test Liferay Portal and Liferay Commerce  against newer major releases of operating systems, open source app servers, browsers, and open source databases (we regularly update the bundled upstream libraries to fix bugs or take advantage of new features in the open source we depend on). 

Liferay Portal 7.4 GA50 and Liferay Commerce 4.0 GA50 were tested extensively for use with the following Application/Database Servers: 

Application Server

  • Tomcat 9.0

  • Wildfly 18.0, 23.0


  • MySQL 5.7, 8.0

  • MariaDB 10.2, 10.4, 10.6

  • PostgreSQL 12.x, 13.x, 14.x


  • IBM J9 JDK 8

  • Oracle JDK 8

  • Oracle JDK 11

  • All Java Technical Compatibility Kit (TCK) compliant builds of Java 11 and Java 8

Search Engine Compatibility Matrix

Source Code

Source is available as a zip archive on the release page, or on its home on GitHub. If you're interested in contributing, take a look at our contribution page.

Bug Reporting

If you believe you have encountered a bug in the new release you can report your issue by following the bug reporting instructions.

Getting Support

Support is provided by our awesome community. Please visit helping a developer page for more details on how you can receive support.

Fixes and Known Issues