build(deps): bump deepmerge from 3.0.1 to 4.0.0 in /docs

Bumps [deepmerge](https://github.com/toumorokoshi/deepmerge) from 3.0.1 to 4.0.0. - [Release notes](https://github.com/toumorokoshi/deepmerge/releases) - [Commits](https://github.com/toumorokoshi/deepmerge/compare/v3.0.1...v4.0.0) --- updated-dependencies: - dependency-name: deepmerge dependency-version: 4.0.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
2026-11-04 15:59:27 +00:00 · 2026-11-04 08:33:11 +00:00
2 changed files with 6 additions and 6 deletions
@@ -60,9 +60,9 @@ There are optional volume paths that can be attached to supply content to be cop

 By default, the [environment variable processing](../configuration/interpolating.md) is performed on synchronized files that match the expected suffixes in `REPLACE_ENV_SUFFIXES` (by default "yml,yaml,txt,cfg,conf,properties,hjson,json,tml,toml") and are not excluded by `REPLACE_ENV_VARIABLES_EXCLUDES` and `REPLACE_ENV_VARIABLES_EXCLUDE_PATHS`. This processing can be disabled by setting `REPLACE_ENV_DURING_SYNC` to `false`.

-If you want old mods/plugins to be removed before the content is brought over from those attach points, then add `-e REMOVE_OLD_MODS=TRUE`. You can fine tune the removal process by specifying the `REMOVE_OLD_MODS_INCLUDE` and `REMOVE_OLD_MODS_EXCLUDE` variables, which are comma separated lists of file glob patterns. If a directory is excluded, then it and all of its contents are excluded. By default, `REMOVE_OLD_MODS_INCLUDE` is `*.jar,*-version.json`, so jars and the `*-version.json` files are removed.
+If you want old mods/plugins to be removed before the content is brought over from those attach points, then add `-e REMOVE_OLD_MODS=TRUE`. You can fine tune the removal process by specifying the `REMOVE_OLD_MODS_INCLUDE` and `REMOVE_OLD_MODS_EXCLUDE` variables, which are comma separated lists of file glob patterns. If a directory is excluded, then it and all of its contents are excluded. By default, only jars are removed. 

-You can also specify the `REMOVE_OLD_MODS_DEPTH` (default is 1) variable to only delete files up to a certain level. With the default, only files directly inside the `plugins/` or `mods/` directory are removed.
+You can also specify the `REMOVE_OLD_MODS_DEPTH` (default is 16) variable to only delete files up to a certain level.

 For example: `-e REMOVE_OLD_MODS=TRUE -e REMOVE_OLD_MODS_INCLUDE="*.jar" -e REMOVE_OLD_MODS_DEPTH=1` will remove all old jar files that are directly inside the `plugins/` or `mods/` directory.

@@ -301,4 +301,4 @@ docker run -d -e REMOVE_OLD_MODS=TRUE -e MODPACK=http://www.example.com/mods/mod

 !!! danger 

-    Files in the `mods` and `plugins` directories that match `REMOVE_OLD_MODS_INCLUDE` (by default, jars and `*-version.json` files directly inside them) will be deleted before unpacking new content from the MODPACK or MODS.
+    All content of the `mods` or `plugins` directory will be deleted before unpacking new content from the MODPACK or MODS.
@@ -1,6 +1,6 @@
 click==8.5.0
 colorama==0.4.6
-deepmerge==3.0.1
+deepmerge==4.0.0
 ghp-import==2.1.0
 griffe==2.4.1
 Jinja2==3.1.6
@@ -14,7 +14,7 @@ mkdocstrings==1.0.8
 mkdocstrings-python==2.0.10
 packaging==26.3
 pathspec==1.1.1
-platformdirs==4.14.2
+platformdirs==4.13.5
 Pygments==2.21.0
 pymdown-extensions==12.3
 python-dateutil==3.0.0
@@ -22,4 +22,4 @@ PyYAML==6.0.3
 pyyaml_env_tag==1.1
 six==1.17.0
 watchdog==6.0.0
-zensical==0.0.74
+zensical==0.0.72