Releases: scandipwa/create-magento-app
v1.11.0
Bug Fixes and Improvements!
Improvements
- Added
--max_allowed_packet
option to MySQL container start command. - Added Composer version check to cli command.
- Added Composer version and Composer location to status command output.
- Added supported ScandiPWA versions to Magento version selector.
Bug Fixes
-
Correct composer version installation.
Before, if your Magento project was created using Composer 1 and then you upgraded the Magento version to use Composer 2, CMA wouldn't notice and in the end, you have ended up with composer dependencies issues.
Now it will warn you that your current Composer version is incorrect and suggest installing the correct one.
-
Fixed typo in Composer version retriever.
v1.11.0-alpha.1
- Added option to run project with incorrect Composer version anyway as a default.
v1.11.0-alpha.0
Bug Fixes
- Correct composer version installation.
Before, if your Magento project was created using Composer 1 and then you upgraded the Magento version to use Composer 2, CMA wouldn't notice and in the end, you have ended up with composer dependencies issues.
Now it will warn you that your current Composer version is incorrect and suggest installing the correct one.
v1.10.0
New status command look, import-db improvements and new Magento versions support!
What's New
- CMA now supports Magento version 2.4.3, 2.4.2-p2 and 2.3.7-p1!
- status command has new look!
Miscellaneous
- Refactored DB sanitizing after database dump import.
Now it should be faster overall. - Added initial Magento setup to import-db command, so it can be used even on empty CMA instances.
- Added some options to mysqldump in import-db command. 30a6e31
- Rollback use of
mysql
to import db dump asmysqlimport
has weird issues with permissions. 2275bed - Source code has been refactored a bit to keep code consistency and follow our eslint rules.
Bug FIxes
v1.9.1
Bug Fixes!
Bug Fixes
- Fixed error which lead to Cannot read property 'scandipwa' of null
v1.9.0
Quality update!
What's New
- Link command got the verbose option.
- URN generation is now built-in start command!
Magento documentation available here! - Analytics is on!
Analytics help us to collect data about errors or possible slow-downs and help us to identify areas that should be fixed or improved!
Learn more here!
Miscellaneous
- Start command console output now has sections.
- The first section is about your Magento current status, where it is accessible and contains credentials for the admin panel.
- The second section will be about the ScandiPWA theme.
If CMA detects that you have the ScandiPWA theme installed, it will print commands to correctly run it in development mode. - The last section will appear only if your CMA version is out of date.
- Setup persisted query in the start command task was moved to be right after Magento install was done to the DB.
Now setup should not break if you have the theme installed but PQ is not yet set up. - Link command now updates
env.php
for PQ setup and the PQ setup itself was moved to be before theme build. env.php
parser error prints file result to the error message.
If your PHP instance is misconfigured for some reason you will know it right away.- Start command now will not recreate the Docker network for your project.
Should save some time during startup - Import dump changes:
- DB sanitizing now should be faster due to query optimizations.
- Import of dump is now done using mysqlimport utility instead of
cat dump
file and pumping stream directly to MySQL as a query. - Added more tables to sanitize table list:
review
,review_detail
,review_entity_summary
,review_store
andreport_event
.
Bug FIxes
- Added
LDFLAGS
env variable to macOS PHP compilation stage which should fix some issues with OpenSSL compilation. 9dbdcaf
v1.8.1
v1.8.0
IMPORTANT COMPATIBILITY CHANGES, Improved XDebug 2 support, compressing for import-db
from remote databases and more!
Important Changes
Recently was discovered a bug in prefix generation.
In general, if you install and run a CMA project in a directory with a name containing dots (.), this was treated as a file name, so everything after a dot was thrown away.
This could lead to interference between projects since project-2.4.1
was using the same prefix as project-2.4.2
, although we use folder creation timestamp with folder name, so the chance of this is very low.
For that reason, since this release this issue is fixed, now the full folder name is used and old MySQL, ElasticSearch and Redis volumes will be automatically converted to new use new prefixes when you run start command.
However, IF you try downgrading to an older version CMA, your setup will not have data from new volumes.
What's New
- XDebug 2 support!
Previously only XDebug 3 configuration was used so it might not be working with XDebug 2. Now it should work as expected. - XDebug extension is not installed by default.
Previously, XDebug was installed but disabled through options inphp.ini
file. Now it's not installed and enabled unless you run project in debug mode. - Importing database from a remote server (ssh) now uses dump compression by default.
If, for some reason, you don't want to use compression, use the new optionno-compress
. - Docker can be automatically installed on the supported platform: Linux!
For macOS and Windows, you will still get a message with instructions on installing Docker on your system.
Miscellaneous
- Improved validation of local
auth.json
file. - start command received new option
-v, --verbose
.
Now by default logs from Magento install & setup & upgrade will not be shown in the console, but if you need them, use this option.
Bug FIxes
- ElasticSearch container option
xpack.ml.enabled
is now enabled correctly on macOS systems. 71c67cb
v1.7.0
Magento version 2.3.x support, automatic PHPBrew install and more!
What's New
- Magento version 2.3.x are supported now!
This includes all released versions as well as patches. - Magento 2.4.2-p1 is now supported as well!
- PHPBrew will now install automatically for each supported platform!
auth.json
file is now supported as well!
Using the globalCOMPOSER_AUTH
environmental variable is not required anymore.
Miscellaneous
update-env
script is also checking for redis session & cache host values.- Magento
setup:install
now will use--cleanup-database
option only if the install was unsuccessful on the first try. - In the
import-db
commandmagento index:reindex
command will run only after the Magento setup is finished using the new dump. - Added error handlers for JSON parsers so error messages are more meaningful.
- Docker network for the project is now removed during the stop task.
This should prevent docker networks from flooding.
See limitations docs. - Converting legacy magento-docker setup to CMA guide is already available!
- Our repository now has every ScandiPWA supported Magento version in sample-packages folder!
Bug Fixes
- Fixed
safe-regex-extract
throwing an error if no result was found. b4de6cd
v.1.6.1
Quality of Life improvements!
What's New
- import-db command now has --with-customers-data option, which will include customers and orders data into dump files and won't delete them while optimising the database task.
- When importing remote database using import-db command, CMA will check if dump files already exist on the remote server and ask the user if he wants to make a new dump or use existing on the remote server.
Miscellaneous
- 9003 port is added to the permanent port ignore list for CMA because otherwise PHP-FPM can take it and it will be impossible to debug the project.
NOTE If your PHP-FPM instance already using port 9003, you need to manually alter theport-config.json
file in thenode_modules/.create-magento-app-cache
folder or update to this version your instances. - Internal calls for magento
setup:install
andsetup:upgrade
commands now include--no-interaction
options, so it should prevent Magento installation and migration from freezing. - Connection to MySQL now checks if MySQL container is starting and extends connection time and tells the user about it.
Bug Fixes
- Added startup option to MySQL container
--default-authentication-plugin=mysql_native_password
which should resolve error Response: SQLSTATE[HY000] [2054] The server requested authentication method unknown to the client
NOTE If you are experiencing this issue and you updated to this version, you will need to delete MySQL volume so it will initialize using the correct authentication method.