@@ -48,12 +48,15 @@ Command line equivalent (takes precedence):
4848[`stack build --[no-]allow-newer`](../../commands/build_command.md#-no-allow-newer-flag)
4949flag
5050
51- Whether to ignore lower and upper version bounds in Cabal files.
51+ !!! warning
5252
53- !!! info
53+ This configuration option is misnamed. It causes Stack to ignore all the
54+ bounds in the relevant Cabal file(s), not only upper bounds. The name was
55+ chosen to match the `--allow-newer` option introduced in `Cabal-1.20.0.0`.
5456
55- The name `allow-newer` was chosen to match a commonly-used Cabal option
56- which ignored only upper bounds.
57+ Whether to ignore all version bounds (upper and lower) in Cabal files. See the
58+ [`allow-newer-deps`](#allow-newer-deps) configuration option to specify the
59+ scope of application when `allow-newer` is `true`.
5760
5861~~~yaml
5962allow-newer : true
@@ -63,15 +66,20 @@ allow-newer: true
6366
6467[:octicons-tag-24 : 2.9.3](https://github.com/commercialhaskell/stack/releases/tag/v2.9.3)
6568
66- Default : ` none`
69+ Default : all packages (if `allow-newer` is `true`)
70+
71+ See the [`allow-newer`](#allow-newer) configuration option.
72+
73+ When `allow-newer` is `false`, this option has no effect (but warns).
6774
68- Determines a subset of packages to which `allow-newer` should apply. This option
69- has no effect (but warns) if `allow-newer` is `false`.
75+ When `allow-newer` is `true`, this option specifies the scope of application
76+ for `allow-newer`. That is, the set of packages for which all version bounds
77+ (upper and lower) should be ignored in the packages' Cabal files.
7078
7179~~~yaml
7280allow-newer-deps :
73- - foo
74- - bar
81+ - myPackageA
82+ - myPackageB
7583~~~
7684
7785# # apply-ghc-options
0 commit comments