Disable the http:cache:warm:up step for Shopware 6.6+ #4041
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
antonmedv
approved these changes
Mar 24, 2025
|
Hi @antonmedv, would be nice to have this change in version 7, because version 8 is still in alpha. Are there any plans for version 7.5.13? |
|
Not right now. I'm planning to move with v8 release soon. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We've seen a few complaints about how Shopware 6.6+ appeared to have dropped support for http:cache:warm:up. This is why we've added conditional logic to check the current shopware version, very similar to how Magento's version check works as can be seen here.
The change in Shopware was loosely mentioned here: https://github.com/shopware/shopware/blob/932d232e999f06cf340ed00708047b9721b253b0/UPGRADE-6.6.md?plain=1#L1035
Bug fix #…?
New feature?
BC breaks?
Tests added?
Docs added?