Update for the dev package to use composer install vs. composer update during zip creation. Updates to composer packages can be done manually during development as needed.

Author: brianhogg

packages/dev/CHANGELOG.md

@@ -1,5 +1,11 @@
 @lifterlms/dev CHANGELOG
 ========================
+v0.2.3 - 2025-12-19
+----------
+
+* Use `composer install` vs. `composer update` during zip creation.
+
+
 v0.2.2 - 2024-04-18
 ----------
 

packages/dev/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lifterlms/dev",
-  "version": "0.2.2",
+  "version": "0.2.3",
   "description": "Developer's CLI for managing, building, and deploying LifterLMS projects.",
   "author": "Team LifterLMS <dev@lifterlms.com>",
   "license": "GPL-3.0-or-later",

packages/dev/src/utils/create-dist-file.js

@@ -53,7 +53,7 @@ module.exports = ( distDir, silent, log = () => {} ) => {
 	// If we have composer dependencies, reinstall with no dev requirements or scripts.
 	if ( composer ) {
 		log( 'Installing composer production dependencies...' );
-		execSync( `composer update --no-dev --no-scripts`, silent );
+		execSync( `composer install --no-dev --no-scripts`, silent );
 		execSync( `rm composer.lock`, true );
 	}
 
@@ -80,7 +80,7 @@ module.exports = ( distDir, silent, log = () => {} ) => {
 	// If we have composer dependencies, reinstall with dev requirements when we're done.
 	if ( composer ) {
 		log( 'Reinstalling all composer dependencies...' );
-		execSync( `composer update`, silent );
+		execSync( `composer install`, silent );
 	}
 
 	return name;