Release preparation - Step D

Author: mpilgrem

ChangeLog.md

@@ -1,6 +1,6 @@
 # Changelog
 
-## Unreleased changes
+## v4.1.0.1 (release candidate)
 
 Release notes:
 
@@ -11,16 +11,16 @@ Release notes:
 
 Major changes:
 
-* Stack now supports GHC's Backpack module system for cross-package use. When a
-  package uses `signatures` and `mixins` to depend on an abstract interface
-  provided by another package, Stack automatically creates the extra
-  instantiation build steps that Cabal requires. This includes support for
-  explicit renaming, multiple instantiations of the same indefinite package,
-  transitive signature chains, sub-library signatures, and indefinite packages
-  from Hackage or snapshots. See the
+* Stack now supports GHC's Backpack module system for cross-package use.
+  (Private Backpack, where signatures and implementations are in the same
+  package, was already supported.) When a package uses `signatures` and `mixins`
+  to depend on an abstract interface provided by another package, Stack
+  automatically creates the extra instantiation build steps that Cabal requires.
+  This includes support for explicit renaming, multiple instantiations of the
+  same indefinite package, transitive signature chains, sub-library signatures,
+  and indefinite package from Hackage or snapshots. See the
   [Backpack topic](https://docs.haskellstack.org/en/stable/topics/backpack/) for
-  details. (Private Backpack, where signatures and implementations live in the
-  same package, has always worked without changes.)
+  details.
 
 Behavior changes:
 
@@ -43,17 +43,10 @@ Other enhancements:
 
 Bug fixes:
 
-* `stack test --no-rerun-tests` correctly skips test suites that have
-  previously been built and run successfully, including for non-Backpack
-  packages built by the per-component planner.
-* Stack's per-component build planner correctly handles the cross-package
-  test/library cycle shape from issue #6905: project package A's library
-  depending on project package B's library, with B's test suite depending on A,
-  builds in the right order with the right configure flags.
 * If snapshot locations are cyclic, Stack reports an error rather than going
   round in circles.
 
-##  v3.11.1 - 2026-06-13
+## v3.11.1 - 2026-06-13
 
 **Changes since v3.9.3:**
 

cabal.config

@@ -181,7 +181,7 @@ constraints:
   , silently ==1.2.5.4
   , split ==0.2.5
   , splitmix ==0.1.3.2
-  , stack ==4.1.0.0
+  , stack ==4.1.0.1
   , static-bytes ==0.2.0
   , stm ==2.5.3.1
   , stm-chans ==3.0.0.11

doc/topics/nix_integration.md

@@ -33,7 +33,7 @@ C libraries that you would normally install manually.
 Nix's `nix-shell` starts an interactive shell based on a Nix expression. Stack
 can automatically create a Nix build environment in the background using
 `nix-instantiate` to produce a store derivation and `nix-shell` with that store
-derivation. This two-step process (since Stack UNRELEASED) allows Stack to
+derivation. This two-step process (since Stack 4.1.1) allows Stack to
 report separately any errors in producing the store derivation. There are two
 alternative options to create such a build environment:
 
@@ -435,7 +435,7 @@ nix:
   # A list of strings, empty by default. Additional options that will be passed
   # verbatim to the `nix-instantiate` command.
   #
-  # Since Stack UNRELEASED
+  # Since Stack 4.1.1
   nix-instantiate-options: []
 
   # A list of strings, empty by default. Additional options that will be passed

package.yaml

@@ -2,7 +2,7 @@
 spec-version: 0.35.0
 
 name: stack
-version: '4.1.0.0'
+version: '4.1.0.1'
 synopsis: A program for developing Haskell projects
 description: |
   Stack (the Haskell Tool Stack) is a program for developing Haskell projects.