diff --git a/.tito/packages/mock b/.tito/packages/mock
index 142453be8..6cccbd8fe 100644
--- a/.tito/packages/mock
+++ b/.tito/packages/mock
@@ -1 +1 @@
-5.6-1 mock/
+5.7-1 mock/
diff --git a/.tito/packages/mock-core-configs b/.tito/packages/mock-core-configs
index c2aa7d1b3..b80548ce8 100644
--- a/.tito/packages/mock-core-configs
+++ b/.tito/packages/mock-core-configs
@@ -1 +1 @@
-41.2-1 mock-core-configs/
+41.3-1 mock-core-configs/
diff --git a/docs/Release-Notes-5.7.md b/docs/Release-Notes-5.7.md
new file mode 100644
index 000000000..6cfa6b7a8
--- /dev/null
+++ b/docs/Release-Notes-5.7.md
@@ -0,0 +1,189 @@
+---
+layout: default
+title: Release Notes - Mock 5.7 (+configs v41.3)
+---
+
+## [Release 5.7](https://rpm-software-management.github.io/mock/Release-Notes-5.7) - 2024-09-26
+
+### New features and important changes
+
+- Support for [hermetic builds](feature-hermetic-builds) has [been][PR#1393]
+  [implemented][PR#1449].  This update introduces two new command-line options:
+  `--calculate-build-deps` and `--hermetic-build`, along with the new
+  `mock-hermetic-repo(1)` utility.
+
+  Additionally, this change introduces a new [`buildroot_lock`
+  plugin](Plugin-BuildrootLock), which generates a new artifact in the buildroot—a
+  buildroot *lockfile*.  Users can enable this plugin explicitly by setting
+  `config_opts["plugin_conf"]["buildroot_lock_enable"] = True`.
+
+- This version addresses [issue#521][], which requested a cleanup option for
+  all chroots.  A [new][PR#1337] option, `--scrub-all-chroots`, has been
+  added.  It can detect leftovers in `/var/lib/mock` or `/var/cache/mock`
+  and make multiple `mock --scrub=all` calls accordingly.
+
+- Alias `dnf4` added for the `package_manager = dnf`.
+
+  The options specific to DNF4, previously prefixed with `dnf_*`, have been
+  renamed to `dnf4_*` too to avoid confusion with `dnf5_*` options.  For backward
+  compatibility, the `dnf_*` prefixed variants still work, so these config pairs
+  are equivalent:
+
+  ```python
+  config_opts['dnf4_install_cmd'] = 'install python3-dnf python3-dnf-plugins-core'
+  config_opts['dnf_install_cmd'] = 'install python3-dnf python3-dnf-plugins-core'
+
+  config_opts['package_manager'] = 'dnf4'
+  config_opts['package_manager'] = 'dnf'
+  ```
+
+  Some of the `dnf_*` options remain unchanged because they are universal and used
+  with DNF4, DNF5, or YUM, e.g., `dnf_vars`.
+
+  While working on this rename, the rarely used `system_<PM>_command` options have
+  been changed to `<PM>_system_command` to visually align with the rest of the
+  package-manager-specific options. The old variants are still accepted.
+
+- The `--addrepo` option has been updated to affect both the bootstrap chroot
+  installation and the buildroot installation, as requested in [issue#1414][].
+  However, be cautious, as Mock [aggressively caches the bootstrap][issue#1289].
+  Always remember to run `mock -r <chroot> --scrub=bootstrap` first.
+  Additionally, as more chroots are being switched to `bootstrap_image_ready =
+  True`, you'll likely need to use `--addrepo` **in combination with**
+  `--no-bootstrap-image`; otherwise, the bootstrap chroot installation will remain
+  unaffected.
+
+- There's a new `config_opts['bootstrap_image_skip_pull']` option that allows you
+  to skip image pulling (running the `podman pull` command by Mock) when preparing
+  the bootstrap chroot.  This is useful if `podman pull` is failing, for example,
+  when the registry is temporarily or permanently unavailable, but the local image
+  exists, or if the image reference is pointing at a local-only image.
+
+- There's a new [ccache](Plugin-CCache) plugin option
+  `config_opts['plugin_conf']['ccache_opts']['show_stats']`; if set to `True`,
+  Mock prints the ccache statistics (hits/misses) to logs.
+
+- A new option `debug` has been [added][PR#1408] to the ccache plugin. Setting
+  it to `True` creates per-object debug files that are helpful when debugging
+  unexpected cache misses, see [ccache docs][ccache-docs-debug].
+
+- A new option `hashdir` has been [added][PR#1399] to the ccache plugin. Setting
+  it to `False` excludes the build working directory from the hash used to
+  distinguish two compilations when generating debuginfo. While this allows the
+  compiler cache to be shared across different package NEVRs, it might cause the
+  debuginfo to be incorrect.
+  The option can be used for issue bisecting if running the debugger is
+  unnecessary ([issue#1395][]).
+
+- New Mock RPM package provides the systemd-sysusers drop-in configuration file
+  for automatic `mock 135` group ID allocation.  See [rpm docs][] for more info.
+
+
+### Bugfixes
+
+- The `installed_pkgs.log` — generated by the `package_state` plugin — was
+  [previously generated too early][issue#1429], after the static build
+  requirements were installed but **before** the dynamic build requirements were
+  resolved and installed. This led to incorrect chroot introspection for the end
+  user, as the reported set of packages needed to build the given package was
+  incomplete.  The new Mock version generates the `installed_pkgs.log` file after
+  the dynamic build requirements are installed.
+
+
+- De-duplicating bootstrap mount points for local repositories used with `--chain`
+  or `--localrepo=file:///repo/on/host`.  Caused eventual problems during
+  `--scrub=bootstrap`.  This bug existed in Mock <= 5.6, but after fixing the
+  [issue#1414][], it got exposed by our test suite.  Related issues include
+  [issue#357][] ([commit#a0a2cba3][]) and [issue#381][] ([commit#16462acc][]).
+
+- Previously, mock.rpm created file in `/usr/share/doc/mock` directory but did
+  did own this directory.
+
+- The fuse-overlayfs package is not installed in the Fedora container images
+  by default. We need to explicitly install it, otherwise running Mock inside of
+  a container won't work.
+
+- Previously, the `nspawn_args` configuration value was not applied in multiple
+  internal `doChroot()` calls.  This could cause issues when custom nspawn
+  arguments were needed everywhere (see [PR#1410][]).  Now, `doChroot()`
+  automatically applies `nspawn_args`, shifting the responsibility from callers to
+  callee.
+
+- Several internal code locations attempt to ensure that the result directory
+  exists, creating it if necessary.  However, these locations handled it
+  inconsistently, sometimes neglecting to [change the ownership][issue#1467] of
+  the result directory.  Now, all locations use a single method dedicated to
+  result directory preparation.
+
+
+### Mock Core Configs changes
+
+- The GPG key locations for the CentOS Stream 10 Appstream debuginfo
+  and Extras Common repositories were updated to point to the correct
+  GPG keys.
+
+- Anolis-7 has been EOLed at 2024-06-30. We moved the configs to `eol` directory.
+
+- The CentOS Stream 10 configuration has been updated to use
+  `quay.io/centos/centos:stream10-development` as its bootstrap image.  Since
+  this image [already has the `python3-dnf-plugins-core` package
+  installed](https://issues.redhat.com/browse/CS-2506), the configuration is also
+  updated to set `bootstrap_image_ready = True`.  This means the image can be
+  used "as is" to bootstrap the DNF stack without installing any additional
+  packages into the prepared bootstrap chroot, significantly speeding up
+  bootstrap preparation.
+
+- The centos-stream-9 (and transitively centos-stream+epel-9) configuration has
+  been fixed to rely on "bootstrap image" readiness for Mock builds, see
+  [issue#1442][].
+
+- OpenSuse Leap 15.4 EOLed at 07 Dec 2023 so we moved the configs to `eol` directory.
+
+- We [updated the configuration][PR#1195] files for chroots that still use older
+  RPM versions (v4.18 and earlier), which affects RHEL/CentOS 9 and older.  These
+  older RPM versions were built with an incorrect default for the `%_host_cpu`
+  macro in `ppc64le` chroots, where the macro incorrectly resolved to
+  `powerpc64le` instead of `ppc64le`.
+
+  This incorrect value caused issues during architecture validation, such as when
+  checking `ExclusiveArch: ppc64le` for `BuildArch: noarch` packages (done
+  in-chroot by `/bin/rpmbuild`).
+
+  The incorrect macro value has now been overridden in the relevant `ppc64le`
+  configuration files in Mock, ensuring that `ExcludeArch` and `ExclusiveArch`
+  validations resolve correctly.
+
+#### Following contributors contributed to this release:
+
+- Brian J. Murrell
+- Carl George
+- Jakub Kadlcik
+- Jiri Kyjovsky
+- Julian Sikorski
+- Miroslav Suchý
+- Nils Philippsen
+- Thomas Mendorf
+
+Thank you!
+
+
+[PR#1195]: https://github.com/rpm-software-management/mock/pull/1195
+[issue#521]: https://github.com/rpm-software-management/mock/issues/521
+[PR#1399]: https://github.com/rpm-software-management/mock/pull/1399
+[commit#a0a2cba3]: https://github.com/rpm-software-management/mock/commit/a0a2cba3
+[PR#1337]: https://github.com/rpm-software-management/mock/pull/1337
+[issue#1429]: https://github.com/rpm-software-management/mock/issues/1429
+[commit#16462acc]: https://github.com/rpm-software-management/mock/commit/16462acc
+[issue#1442]: https://github.com/rpm-software-management/mock/issues/1442
+[PR#1408]: https://github.com/rpm-software-management/mock/pull/1408
+[issue#1289]: https://github.com/rpm-software-management/mock/issues/1289
+[issue#1414]: https://github.com/rpm-software-management/mock/issues/1414
+[issue#381]: https://github.com/rpm-software-management/mock/issues/381
+[PR#1393]: https://github.com/rpm-software-management/mock/pull/1393
+[issue#357]: https://github.com/rpm-software-management/mock/issues/357
+[issue#1467]: https://github.com/rpm-software-management/mock/issues/1467
+[issue#1395]: https://github.com/rpm-software-management/mock/issues/1395
+[PR#1410]: https://github.com/rpm-software-management/mock/pull/1410
+[PR#1449]: https://github.com/rpm-software-management/mock/pull/1449
+[ccache-docs-debug]: https://ccache.dev/manual/4.10.html#config_debug
+[rpm docs]: https://rpm-software-management.github.io/rpm/manual/users_and_groups.html
diff --git a/docs/index.md b/docs/index.md
index c5e460409..f1cb0caa0 100644
--- a/docs/index.md
+++ b/docs/index.md
@@ -69,7 +69,8 @@ Versions in Linux distributions:
 
 
 ## Release Notes
-* [Configs 41.1](Release-Notes-Configs-41.1) - EL7 configs EOL. F38 EOL. F41 branched.
+* [5.7 and Configs 41.3](Release-Notes-5.7) - Support for isolated builds added.  DNF4 = DNF.  Option `--scrub-all-chroots` added.
+* [Configs 41.1 (and 41.2)](Release-Notes-Configs-41.1) - EL7 configs EOL. F38 EOL. F41 branched.
 * [Configs 40.6](Release-Notes-Configs-40.6) - CentOS Stream 10 uses mirrored repositories.
 * [Configs 40.5](Release-Notes-Configs-40.5) - Fedora 38 moved to EOL. CentOS Stream 8 moved to vault.
 * [5.6](Release-Notes-5.6) - Improved performance of bash completion, don't use `--allowerasing` for commands that doesn't provide it, fixed "no space left" tracebacks, new Circle Linux 9 configs, Mageia Cauldron i686, fixed Fedora ELN.
diff --git a/mock-core-configs/mock-core-configs.spec b/mock-core-configs/mock-core-configs.spec
index 3af52b8d4..2c45b929a 100644
--- a/mock-core-configs/mock-core-configs.spec
+++ b/mock-core-configs/mock-core-configs.spec
@@ -3,7 +3,7 @@
 %endif
 
 Name:       mock-core-configs
-Version:    41.2
+Version:    41.3
 Release:    1%{?dist}
 Summary:    Mock core config files basic chroots
 
@@ -149,6 +149,14 @@ fi
 %ghost %config(noreplace,missingok) %{_sysconfdir}/mock/default.cfg
 
 %changelog
+* Thu Sep 26 2024 Pavel Raiskup <praiskup@redhat.com> 41.3-1
+- move anolis-7 to eol directory (msuchy@redhat.com)
+- move opensuse-leap-15.4 to eol directory (msuchy@redhat.com)
+- configs: the stream9 image is "ready" for Mock bootstrap
+- enable bootstrap container for CentOS Stream 10 (carlwgeorge@gmail.com)
+- configs: replace `powerpc64le` with `ppc64le` in the `%%_host_cpu` macro
+- fix EOL template locations for CentOS7/EPEL7 (thomas.mendorf@ebf.com)
+
 * Thu Aug 15 2024 Pavel Raiskup <praiskup@redhat.com> 41.2-1
 - fix centos-stream+epel-10-s390x /bin/sed typo
 
diff --git a/mock/mock.spec b/mock/mock.spec
index b2abafee2..d231b7a72 100644
--- a/mock/mock.spec
+++ b/mock/mock.spec
@@ -6,7 +6,7 @@
 
 Summary: Builds packages inside chroots
 Name: mock
-Version: 5.6.post1
+Version: 5.7
 Release: 1%{?dist}
 License: GPL-2.0-or-later
 # Source is created by
@@ -313,6 +313,27 @@ pylint-3 py/mockbuild/ py/*.py py/mockbuild/plugins/* || :
 %config(noreplace) %{_sysusersdir}/mock.conf
 
 %changelog
+* Thu Sep 26 2024 Pavel Raiskup <praiskup@redhat.com> 5.7-1
+- hermetic: new mode to do fully-offline builds
+- new --scrub-all-chroots option
+- make "dnf4" equivalent to "dnf"
+- chroot_scan: create result directory with appropriate permissions
+- chain: No need to re-create resultdir
+- de-duplicate the local-repo mountpoint in bootstrap
+- respect `nspawn_args` whenever `doChroot` is called
+- ensure --addrepo option also affects bootstrap
+- de-duplicate two opinionated doChroot() calls
+- show ccache stats at the end of the build (brian@interlinx.bc.ca)
+- add `debug` option to the ccache plugin (belegdol@fedoraproject.org)
+- add runtime dependency on fuse-overlayfs (frostyx@email.cz)
+- skip the "podman pull" for bootstrap when not needed
+- package_state: the installed_pkgs.log file now covers dynamic builddeps
+- don’t ship rpmautospec plugin with main package (nils@redhat.com)
+- clean up of macros referencing rhel7 (msuchy@redhat.com)
+- enable RPM sysusers integration (j1.kyjovsky@gmail.com)
+- add hashdir option to ccache plugin (belegdol@fedoraproject.org)
+- own /usr/share/doc/mock (msuchy@redhat.com)
+
 * Tue May 14 2024 Jakub Kadlcik <frostyx@email.cz> 5.6-1
 - scm: Open stdout in text mode for Git timestamp subprocesses
   (fedora.dm0@gmail.com)
diff --git a/releng/release-notes-next/addrepo-affects-bootstrap.feature b/releng/release-notes-next/addrepo-affects-bootstrap.feature
deleted file mode 100644
index a82e71f3a..000000000
--- a/releng/release-notes-next/addrepo-affects-bootstrap.feature
+++ /dev/null
@@ -1,8 +0,0 @@
-The `--addrepo` option has been updated to affect both the bootstrap chroot
-installation and the buildroot installation, as requested in [issue#1414][].
-However, be cautious, as Mock [aggressively caches the bootstrap][issue#1289].
-Always remember to run `mock -r <chroot> --scrub=bootstrap` first.
-Additionally, as more chroots are being switched to `bootstrap_image_ready =
-True`, you'll likely need to use `--addrepo` **in combination with**
-`--no-bootstrap-image`; otherwise, the bootstrap chroot installation will remain
-unaffected.
diff --git a/releng/release-notes-next/anolis-7.config b/releng/release-notes-next/anolis-7.config
deleted file mode 100644
index e93257e59..000000000
--- a/releng/release-notes-next/anolis-7.config
+++ /dev/null
@@ -1 +0,0 @@
-Anolis-7 has been EOLed at 2024-06-30. We moved the configs to `eol` directory.
diff --git a/releng/release-notes-next/bootstrap-skip-image-pull.feature b/releng/release-notes-next/bootstrap-skip-image-pull.feature
deleted file mode 100644
index cf8a3d807..000000000
--- a/releng/release-notes-next/bootstrap-skip-image-pull.feature
+++ /dev/null
@@ -1,5 +0,0 @@
-There's a new `config_opts['bootstrap_image_skip_pull']` option that allows you
-to skip image pulling (running the `podman pull` command by Mock) when preparing
-the bootstrap chroot.  This is useful if `podman pull` is failing, for example,
-when the registry is temporarily or permanently unavailable, but the local image
-exists, or if the image reference is pointing at a local-only image.
diff --git a/releng/release-notes-next/buildroot-mounts-redundancy.bugfix b/releng/release-notes-next/buildroot-mounts-redundancy.bugfix
deleted file mode 100644
index 200e77b09..000000000
--- a/releng/release-notes-next/buildroot-mounts-redundancy.bugfix
+++ /dev/null
@@ -1,5 +0,0 @@
-De-duplicating bootstrap mount points for local repositories used with `--chain`
-or `--localrepo=file:///repo/on/host`.  Caused eventual problems during
-`--scrub=bootstrap`.  This bug existed in Mock <= 5.6, but after fixing the
-[issue#1414][], it got exposed by our test suite.  Related issues include
-[issue#357][] ([commit#a0a2cba3][]) and [issue#381][] ([commit#16462acc][]).
diff --git a/releng/release-notes-next/c10s-bootstrap-ready.config.md b/releng/release-notes-next/c10s-bootstrap-ready.config.md
deleted file mode 100644
index 93d991126..000000000
--- a/releng/release-notes-next/c10s-bootstrap-ready.config.md
+++ /dev/null
@@ -1,8 +0,0 @@
-The CentOS Stream 10 configuration has been updated to use
-`quay.io/centos/centos:stream10-development` as its bootstrap image.  Since
-this image [already has the `python3-dnf-plugins-core` package
-installed](https://issues.redhat.com/browse/CS-2506), the configuration is also
-updated to set `bootstrap_image_ready = True`.  This means the image can be
-used "as is" to bootstrap the DNF stack without installing any additional
-packages into the prepared bootstrap chroot, significantly speeding up
-bootstrap preparation.
diff --git a/releng/release-notes-next/c9s-image-ready.config b/releng/release-notes-next/c9s-image-ready.config
deleted file mode 100644
index 225c47efe..000000000
--- a/releng/release-notes-next/c9s-image-ready.config
+++ /dev/null
@@ -1,3 +0,0 @@
-The centos-stream-9 (and transitively centos-stream+epel-9) configuration has
-been fixed to rely on "bootstrap image" readiness for Mock builds
-[issue#1442][].
diff --git a/releng/release-notes-next/ccache-show-stats.feature b/releng/release-notes-next/ccache-show-stats.feature
deleted file mode 100644
index f33241791..000000000
--- a/releng/release-notes-next/ccache-show-stats.feature
+++ /dev/null
@@ -1,3 +0,0 @@
-There's a new [ccache](Plugin-CCache) plugin option
-`config_opts['plugin_conf']['ccache_opts']['show_stats']`; if set to `True`,
-Mock prints the ccache statistics (hits/misses) to logs.
diff --git a/releng/release-notes-next/ccache_debug.feature b/releng/release-notes-next/ccache_debug.feature
deleted file mode 100644
index 827e8d6c3..000000000
--- a/releng/release-notes-next/ccache_debug.feature
+++ /dev/null
@@ -1,4 +0,0 @@
-A new option `debug` has been [added][PR#1408] to the ccache plugin. Setting
-it to `True` creates per-object debug files that are helpful when debugging
-unexpected cache misses.
-https://ccache.dev/manual/4.10.html#config_debug
\ No newline at end of file
diff --git a/releng/release-notes-next/centos-stream-10-gpg-keys.bugfix b/releng/release-notes-next/centos-stream-10-gpg-keys.bugfix
deleted file mode 100644
index 60df56901..000000000
--- a/releng/release-notes-next/centos-stream-10-gpg-keys.bugfix
+++ /dev/null
@@ -1,3 +0,0 @@
-The GPG key locations for the CentOS Stream 10 Appstream debuginfo
-and Extras Common repositories were updated to point to the correct
-GPG keys.
diff --git a/releng/release-notes-next/dnf4-config-is-alias-to-dnf.feature b/releng/release-notes-next/dnf4-config-is-alias-to-dnf.feature
deleted file mode 100644
index d875901a4..000000000
--- a/releng/release-notes-next/dnf4-config-is-alias-to-dnf.feature
+++ /dev/null
@@ -1,21 +0,0 @@
-Alias `dnf4` added for the `package_manager = dnf`.
-
-The options specific to DNF4, previously prefixed with `dnf_*`, have been
-renamed to `dnf4_*` too to avoid confusion with `dnf5_*` options.  For backward
-compatibility, the `dnf_*` prefixed variants still work, so these config pairs
-are equivalent:
-
-```python
-config_opts['dnf4_install_cmd'] = 'install python3-dnf python3-dnf-plugins-core'
-config_opts['dnf_install_cmd'] = 'install python3-dnf python3-dnf-plugins-core'
-
-config_opts['package_manager'] = 'dnf4'
-config_opts['package_manager'] = 'dnf'
-```
-
-Some of the `dnf_*` options remain unchanged because they are universal and used
-with DNF4, DNF5, or YUM, e.g., `dnf_vars`.
-
-While working on this rename, the rarely used `system_<PM>_command` options have
-been changed to `<PM>_system_command` to visually align with the rest of the
-package-manager-specific options. The old variants are still accepted.
diff --git a/releng/release-notes-next/docdir-ownership.bugfix b/releng/release-notes-next/docdir-ownership.bugfix
deleted file mode 100644
index e880e8ee4..000000000
--- a/releng/release-notes-next/docdir-ownership.bugfix
+++ /dev/null
@@ -1,2 +0,0 @@
-Previously mock.rpm created file in /usr/share/doc/mock directory but did Mock
-did not owned this directory. This directory is now owned by Mock.
diff --git a/releng/release-notes-next/fuse-overlayfs.bugfix b/releng/release-notes-next/fuse-overlayfs.bugfix
deleted file mode 100644
index 4e16b7d5c..000000000
--- a/releng/release-notes-next/fuse-overlayfs.bugfix
+++ /dev/null
@@ -1,3 +0,0 @@
-The fuse-overlayfs package is not installed in the Fedora container images
-by default. We need to explicitly install it, otherwise running Mock inside of
-a container won't work.
diff --git a/releng/release-notes-next/hashdir.feature b/releng/release-notes-next/hashdir.feature
deleted file mode 100644
index e15bbe0d0..000000000
--- a/releng/release-notes-next/hashdir.feature
+++ /dev/null
@@ -1,7 +0,0 @@
-A new option `hashdir` has been [added][PR#1399] to the ccache plugin. Setting
-it to `False` excludes the build working directory from the hash used to
-distinguish two compilations when generating debuginfo. While this allows the
-compiler cache to be shared across different package NEVRs, it might cause the
-debuginfo to be incorrect.
-The option can be used for issue bisecting if running the debugger is
-unnecessary. ([issue#1395][])
diff --git a/releng/release-notes-next/hermetic-build.feature b/releng/release-notes-next/hermetic-build.feature
deleted file mode 100644
index 819096e21..000000000
--- a/releng/release-notes-next/hermetic-build.feature
+++ /dev/null
@@ -1,9 +0,0 @@
-Support for [hermetic builds](feature-hermetic-builds) has been
-[implemented][PR#1393].  This update introduces two new command-line options:
-`--calculate-build-deps` and `--hermetic-build`, along with the new
-`mock-hermetic-repo(1)` utility.
-
-Additionally, this change introduces a new [`buildroot_lock`
-plugin](Plugin-BuildrootLock), which generates a new artifact in the buildroot—a
-buildroot *lockfile*.  Users can enable this plugin explicitly by setting
-`config_opts["plugin_conf"]["buildroot_lock_enable"] = True`.
diff --git a/releng/release-notes-next/leap-15-4.config b/releng/release-notes-next/leap-15-4.config
deleted file mode 100644
index 27941933d..000000000
--- a/releng/release-notes-next/leap-15-4.config
+++ /dev/null
@@ -1 +0,0 @@
-OpenSuse Leap 15.4 EOLed at 07 Dec 2023 so we moved the configs to `eol` directory.
diff --git a/releng/release-notes-next/nspawn-args-chroot-bootstrap.bugfix b/releng/release-notes-next/nspawn-args-chroot-bootstrap.bugfix
deleted file mode 100644
index 30b9a7e3a..000000000
--- a/releng/release-notes-next/nspawn-args-chroot-bootstrap.bugfix
+++ /dev/null
@@ -1,5 +0,0 @@
-Previously, the `nspawn_args` configuration value was not applied in multiple
-internal `doChroot()` calls.  This could cause issues when custom nspawn
-arguments were needed everywhere (see [PR#1410][]).  Now, `doChroot()`
-automatically applies `nspawn_args`, shifting the responsibility from callers to
-callee.
diff --git a/releng/release-notes-next/package-state-after-deps-resolved.bugfix b/releng/release-notes-next/package-state-after-deps-resolved.bugfix
deleted file mode 100644
index 658ac90f4..000000000
--- a/releng/release-notes-next/package-state-after-deps-resolved.bugfix
+++ /dev/null
@@ -1,7 +0,0 @@
-The `installed_pkgs.log` — generated by the `package_state` plugin — was
-[previously generated too early][issue#1429], after the static build
-requirements were installed but **before** the dynamic build requirements were
-resolved and installed. This led to incorrect chroot introspection for the end
-user, as the reported set of packages needed to build the given package was
-incomplete.  The new Mock version generates the `installed_pkgs.log` file after
-the dynamic build requirements are installed.
diff --git a/releng/release-notes-next/ppc64le-not-powerpc64le-host-cpu.config b/releng/release-notes-next/ppc64le-not-powerpc64le-host-cpu.config
deleted file mode 100644
index 930c11860..000000000
--- a/releng/release-notes-next/ppc64le-not-powerpc64le-host-cpu.config
+++ /dev/null
@@ -1,13 +0,0 @@
-We [updated the configuration][PR#1195] files for chroots that still use older
-RPM versions (v4.18 and earlier), which affects RHEL/CentOS 9 and older.  These
-older RPM versions were built with an incorrect default for the `%_host_cpu`
-macro in `ppc64le` chroots, where the macro incorrectly resolved to
-`powerpc64le` instead of `ppc64le`.
-
-This incorrect value caused issues during architecture validation, such as when
-checking `ExclusiveArch: ppc64le` for `BuildArch: noarch` packages (done
-in-chroot by `/bin/rpmbuild`).
-
-The incorrect macro value has now been overridden in the relevant `ppc64le`
-configuration files in Mock, ensuring that `ExcludeArch` and `ExclusiveArch`
-validations resolve correctly.
diff --git a/releng/release-notes-next/scrub-all-chroots.feature b/releng/release-notes-next/scrub-all-chroots.feature
deleted file mode 100644
index d51e333ae..000000000
--- a/releng/release-notes-next/scrub-all-chroots.feature
+++ /dev/null
@@ -1,4 +0,0 @@
-This version addresses [issue#521][], which requested a cleanup option for
-all chroots.  A [new][PR#1337] option, `--scrub-all-chroots`, has been
-added.  It can detect leftovers in `/var/lib/mock` or `/var/cache/mock`
-and make multiple `mock --scrub=all` calls accordingly.
diff --git a/releng/release-notes-next/sysusers-handled-by-rpm.feature b/releng/release-notes-next/sysusers-handled-by-rpm.feature
deleted file mode 100644
index 7c163b740..000000000
--- a/releng/release-notes-next/sysusers-handled-by-rpm.feature
+++ /dev/null
@@ -1,3 +0,0 @@
-New Mock RPM package provides the systemd-sysusers drop-in configuration file for automatic
-`mock 135` group ID allocation.
-https://rpm-software-management.github.io/rpm/manual/users_and_groups.html
diff --git a/releng/release-notes-next/unified-resultdir-preparation.bugfix b/releng/release-notes-next/unified-resultdir-preparation.bugfix
deleted file mode 100644
index 0211f08b2..000000000
--- a/releng/release-notes-next/unified-resultdir-preparation.bugfix
+++ /dev/null
@@ -1,5 +0,0 @@
-Several internal code locations attempt to ensure that the result directory
-exists, creating it if necessary.  However, these locations handled it
-inconsistently, sometimes neglecting to [change the ownership][issue#1467] of
-the result directory.  Now, all locations use a single method dedicated to
-result directory preparation.