How to upgrade the extension

To upgrade the extension, follow these steps:

Back up your store's database and web directory.
Log in to the SSH console of your server and navigate to the root directory of your Magento 2 store.
Run the following command to update the current extension along with all dependencies:
```
composer require mirasvit/module-cataloglabel:* --update-with-dependencies
```
In some cases, the command above may not be applicable, or you may be unable to update only the current module. If that's the case, you will need to upgrade all Mirasvit modules in a bundle. The command above will have no effect in such scenarios. Instead, run the following command to update all Mirasvit modules installed in your store:
```
composer update mirasvit/*
```
If mirasvit/module-cataloglabel-hyva is still installed, the update takes it off by itself: Hyvä support ships inside mirasvit/module-cataloglabel, and newer versions tell composer they replace the retired package. Only versions 2.6.0–2.6.1 refuse to install beside it instead. If you are upgrading to one of those and composer stops with a conflict such as mirasvit/module-cataloglabel … conflicts with mirasvit/module-cataloglabel-hyva …, remove it and run the update again:
```
composer remove mirasvit/module-cataloglabel-hyva
```
Nothing is lost: setup:upgrade also drops the retired Hyva_MirasvitCatalogLabel module name from app/etc/config.php for you.

Re-enable the extension by running the following command:

php -f bin/magento module:enable Mirasvit_Core Mirasvit_CatalogLabel

Install the updates by running the following command:
```
php -f bin/magento setup:upgrade
```
Clean the cache by running the following command:
```
php -f bin/magento cache:clean
```

Deploy the static view files:

rm -rf pub/static/*; rm -rf var/view_preprocessed/*;
php -f bin/magento setup:static-content:deploy

On a Hyvä store, rebuild the theme assets. The extension registers its own Tailwind sources now, which the retired package used to do on its behalf:
```
bin/magento hyva:config:generate
```
```
cd /path/to/theme/web/tailwind/
npm run build-prod
```
Skipping this leaves the labels unpositioned — the theme keeps serving the styles.css it was built with, which knows nothing about the position-* classes the extension puts on a placeholder.