Releases: FrontasticGmbH/frontastic-cli
Releases · FrontasticGmbH/frontastic-cli
2.5.0
2.4.4
2.4.3
2.4.2
2.4.1
2.4.0
New Features
You no longer need to use the --multitenant
parameter when running the
frontastic init
command to initialize your project because a
project is now automatically detected as multi-tenant. Explicitly using the
--multitenant
parameter is still possible, but it will override the detection
and the initialized project will always be considered multi-tenant.
Bugfixes
- The Bundle upload status in the Status pane is now displayed
correctly on two lines instead of being truncated. - If an error occurs when copying log messages with the
c
hotkey, a dedicated
error message now appears in a dialog instead of in the internal log pane for
better visibility. - Some inconsistencies in the dashboard layout are now resolved:
- The message in the Errors pane is now easier to understand.
- In the Startup checks pane, checks are now contextual, meaning that
checks only appear if they apply for the current mode (for example, the
SSH connection check is not displayed for multi-tenant projects).
2.3.1
2.3.0
New Features
- "Distributed trace" log messages in the extension log are now hidden by default. This can be changed in the filter dialog (press F)
Bugfixes
- Fix a bug where the upload command required a frontastic.toml configuration file
- Fix a bug where the upload command would exit with an error when executed as root user
2.2.1
2.2.0
New Features
- New command "upload" to upload staging backend extension builds to the Studio (see documentation for more information)
- New command "scaffold" to create a commercetools Frontend repository from scratch (see documentation for more information)
Bugfixes
- The extension runner manager URL is now fetched on initialization instead of
always using the same. This fixes a problem where the URL need to be manually
adjusted in some cases.