You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: products/cli/extension-commands/configuration.md
+16Lines changed: 16 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,6 +12,8 @@ Many configurations can be changed using a `.shopware-extension.yml` file in the
12
12
Here is an example of a `.shopware-extension.yml` file:
13
13
14
14
```yaml
15
+
compatibility_date: '2026-02-11'
16
+
15
17
build:
16
18
extraBundles:
17
19
- path: src/Foo
@@ -42,6 +44,20 @@ validation:
42
44
43
45
When you edit that file in an editor, you will get autocompletion and hints for the available options.
44
46
47
+
## compatibility_date
48
+
49
+
You can define a `compatibility_date` in `.shopware-extension.yml`:
50
+
51
+
```yaml
52
+
compatibility_date: '2026-02-11'
53
+
```
54
+
55
+
The `compatibility_date` lets Shopware CLI introduce behavior changes without breaking existing projects by default. New or potentially breaking changes are activated only for configurations that opt in with a date at or after the feature's rollout date.
56
+
57
+
- Format: `YYYY-MM-DD`
58
+
- If the field is missing, Shopware CLI uses `2026-02-11` as fallback
59
+
- When missing, Shopware CLI logs a warning during config loading
60
+
45
61
## Environment variables
46
62
47
63
Additionally, you can set environment variables to change the behavior of the CLI. The following environment variables are available:
Copy file name to clipboardExpand all lines: products/cli/project-commands/build.md
+16Lines changed: 16 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -105,6 +105,8 @@ MJML compilation requires the `mjml` package to be installed via NPM in your bui
105
105
You can configure the build process with a `.shopware-project.yml` file. The following options are available:
106
106
107
107
```yaml
108
+
compatibility_date: '2026-02-11'
109
+
108
110
build:
109
111
# Browserlist configuration for Storefront
110
112
browserslist: 'defaults'
@@ -134,6 +136,20 @@ build:
134
136
- custom/static-plugins
135
137
```
136
138
139
+
## compatibility_date
140
+
141
+
You can define a `compatibility_date` in `.shopware-project.yml`:
142
+
143
+
```yaml
144
+
compatibility_date: '2026-02-11'
145
+
```
146
+
147
+
The `compatibility_date` lets Shopware CLI introduce behavior changes without breaking existing projects by default. New or potentially breaking changes are activated only for configurations that opt in with a date at or after the feature's rollout date.
148
+
149
+
- Format: `YYYY-MM-DD`
150
+
- If the field is missing, Shopware CLI uses `2026-02-11` as fallback
151
+
- When missing, Shopware CLI logs a warning during config loading
152
+
137
153
## Supporting bundles
138
154
139
155
Shopware CLI automatically detects plugins and Apps. Custom bundles (classes that extend bundle class from Shopware) cannot be automatically detected as Shopware CLI does not execute any PHP code.
0 commit comments