diff --git a/changelog/build_unittest.dd b/changelog/build_unittest.dd
deleted file mode 100644
index 2574c29..0000000
--- a/changelog/build_unittest.dd
+++ /dev/null
@@ -1,8 +0,0 @@
-Building the special test runner configuration
-
-`dub build --config=unittest --build=unittest[-cov]` can now be used to
-mimic building the test runner executable of `dub test [--coverage]`.
-Note that this doesn't require an existing `unittest` configuration.
-
-`dub describe --config=unittest` allows to derive the path to the
-executable.
diff --git a/changelog/colored_output.dd b/changelog/colored_output.dd
deleted file mode 100644
index 8102feb..0000000
--- a/changelog/colored_output.dd
+++ /dev/null
@@ -1,14 +0,0 @@
-Output will now be colorized
-
-Dub output has been improved to be more human readable,
-which means the most important informations in the output
-will now be colorized / bold.
-
-As is usual with CLI tools, this behavior is automatically
-turned on whether the output is a TTY. To force the old output
-in the presence of a TTY, use `--color=off`. To force colored
-output in the absence of a TTY, use `--color=on`.
-
-The `--color` flag, if set to `on` or `off`, is automatically
-forwarded to the compiler. This is especially useful for CI
-pipelines to ensure human-readable output.
diff --git a/changelog/configy_stricter_parsing.dd b/changelog/configy_stricter_parsing.dd
deleted file mode 100644
index c4deeb7..0000000
--- a/changelog/configy_stricter_parsing.dd
+++ /dev/null
@@ -1,9 +0,0 @@
-dub will now warn on unrecognized fields in `dub.json`, settings, or selections file
-
-Previously, dub was silently accepting anything it didn't recognize
-in `dub.json`, `[dub.]settings.json` and `dub.selections.json`. While the original
-intent was to make forward-compatibility easy, it proved detrimental
-as typos would just mean the user setting was ignored.
-
-From this release, dub will now warn about any entry in its configuration files
-or in `dub.selections.json`. After 10 releases, those warnings will turn into errors.
diff --git a/changelog/cov_ctfe.dd b/changelog/cov_ctfe.dd
deleted file mode 100644
index a6ccb63..0000000
--- a/changelog/cov_ctfe.dd
+++ /dev/null
@@ -1,4 +0,0 @@
-The two new build types `cov-ctfe` and `unittest-cov-ctfe` have been added.
-
-These extend the existing build types `cov` and `unittest-cov` respectively by
-appending `-cov=ctfe` to the set of flags passed to the compiler.
diff --git a/changelog/dpath.dd b/changelog/dpath.dd
deleted file mode 100644
index 098bf00..0000000
--- a/changelog/dpath.dd
+++ /dev/null
@@ -1,34 +0,0 @@
-DUB settings & packages directory placement overhauled
-
-You can now configure where DUB places its downloaded packages and where the user configuration is stored through environment variables or through the dub configuration. You need to use an environment variable or the system-wide dub configuration to specify where the user configuration is stored.
-
-By default DUB stores the packages on
-- Windows: `%APPDATA%/dub/settings.json` + `%LOCALAPPDATA%/dub/packages/`
-- Posix: `$HOME/.dub/{packages/,settings.json}`
-
-now if the `DUB_HOME` environment variable is set it instead stores the packages (and other config) in
-- `$DUB_HOME/{packages/,settings.json}`
-
-alternatively if `DUB_HOME` isn't set, but `DPATH` is set, the following path is used:
-- `$DPATH/dub/{packages/,settings.json}`
-
-The `DPATH` environment variable is intended to be used by all D tooling related things doing user-space installation of things. It can be used to avoid cluttering the home folder.
-
-Additionally to environment variables it is possible to configure the package placement path + settings.json path through DUB's settings.json file. To configure where the user-editable settings.json is placed you need to adjust the system-wide dub configuration.
-
-In the settings.json you can set the following fields:
-
-```json
-{
-    "dubHome": "/path/to/dub", // sets both package store and config location
-}
-```
-
-Additionally, these config paths will have environment variables using the `$VARIABLE` syntax resolved.
-
-The following list describes which path is going to be picked, from top to bottom, stopping whenever one is found:
-
-- `$DUB_HOME` environment variable
-- `$DPATH` environment variable
-- system-wide settings.json: `"dubHome"` property (only for userSettings)
-- most specific settings.json: `"dubHome"` property (only for localRepository)
diff --git a/changelog/exitcodes.dd b/changelog/exitcodes.dd
deleted file mode 100644
index 0ecdb3e..0000000
--- a/changelog/exitcodes.dd
+++ /dev/null
@@ -1,11 +0,0 @@
-DUB command exit codes have been made more consistent
-
-Some dub commands have been adjusted to return exit code 2 instead of exit code 1. Exit code 1 is now always used for usage errors, while exit code 2 is the more generic any error occurred or package failed to load.
-
-The following commands are affected:
-
-- dub clean
-- dub add
-- dub search
-- dub convert
-
diff --git a/changelog/install_uninstall.dd b/changelog/install_uninstall.dd
deleted file mode 100644
index 445c64b..0000000
--- a/changelog/install_uninstall.dd
+++ /dev/null
@@ -1,5 +0,0 @@
-'install' and 'uninstall' commands have been removed
-
-Those commands were long-deprecated aliases to `fetch` and `remove`,
-respectively, and usage of them triggered a warning.
-They are no longer listed as command in help and dub will no longer recognize them.
diff --git a/changelog/make-copies-writable.dd b/changelog/make-copies-writable.dd
deleted file mode 100644
index ce5edef..0000000
--- a/changelog/make-copies-writable.dd
+++ /dev/null
@@ -1,8 +0,0 @@
-When `copyFiles` is used to copy read-only files, it now makes the copy writable.
-
-Previously, if the target file would already exist due to a prior run of Dub, `copyFiles` would produce an access
-denied error because the read-only target could not be overwritten. Note that if you were affected by this behaviour,
-you will need to remove those files by hand once to eliminate these errors.
-
-It is common for version control systems to mark binary files read-only in the working copy, to prevent concurrent
-edits of files in unmergeable formats.
diff --git a/changelog/overrides_deprecated.dd b/changelog/overrides_deprecated.dd
deleted file mode 100644
index eaafbd0..0000000
--- a/changelog/overrides_deprecated.dd
+++ /dev/null
@@ -1,9 +0,0 @@
-The override system is deprecated
-
-Dub had an "override" system, allowing a specific version or version range
-to be overriden by a specific package.
-This override system was developed with a purely version-based approach in mind,
-however since its inception, more ways to specify dependencies have been added,
-making the override approach redundant and less flexible than other approaches.
-From this release, dub will warn you if it finds an override file,
-or when using the `dub add-override` / `dub remove-override` commands.
diff --git a/changelog/subpackage_short_syntax.dd b/changelog/subpackage_short_syntax.dd
deleted file mode 100644
index cf50a10..0000000
--- a/changelog/subpackage_short_syntax.dd
+++ /dev/null
@@ -1,4 +0,0 @@
-The shortcut syntax for "dub run" is now also available for sub packages.
-
-Invoking dub as "dub :subpackage" is now equivalent to "dub run :subpackage",
-analogous to just "dub" being equivalent to "dub run".
diff --git a/changelog/subpackage_upgrade.dd b/changelog/subpackage_upgrade.dd
deleted file mode 100644
index c9a28ce..0000000
--- a/changelog/subpackage_upgrade.dd
+++ /dev/null
@@ -1,5 +0,0 @@
-Upgrading all sub packages at once
-
-A new "-s" switch allows to "dub upgrade" all sub packages together with the
-base package. This aims to provide a better workflow for fully reproducible
-builds and tests.