Create changelogs for 3.14.1.0

Cabal-syntax/ChangeLog.md

@@ -1 +1 @@
-Please see https://github.com/haskell/cabal/blob/master/release-notes/Cabal-3.14.0.0.md
+Please see https://github.com/haskell/cabal/blob/master/release-notes/Cabal-3.14.1.0.md

Cabal/ChangeLog.md

@@ -1,3 +1,6 @@
+# 3.14.1.0 [Hécate](mailto:[email protected]) November 2024
+* See https://github.com/haskell/cabal/blob/master/release-notes/Cabal-3.14.1.0.md
+
 # 3.14.0.0 [Hécate](mailto:[email protected]) September 2024
 * See https://github.com/haskell/cabal/blob/master/release-notes/Cabal-3.14.0.0.md
 

cabal-install-solver/ChangeLog.md

@@ -1 +1 @@
-Please see https://github.com/haskell/cabal/blob/master/release-notes/cabal-install-3.14.0.0.md
+Please see https://github.com/haskell/cabal/blob/master/release-notes/cabal-install-3.14.1.0.md

cabal-install/changelog

@@ -1,5 +1,8 @@
 -*-change-log-*-
 
+3.14.1.0 Hécate <[email protected]> November 2024
+	* See https://github.com/haskell/cabal/blob/master/release-notes/cabal-install-3.14.1.0.md
+
 3.14.0.0 Hécate <[email protected]> September 2024
 	* See https://github.com/haskell/cabal/blob/master/release-notes/cabal-install-3.14.0.0.md
 

release-notes/Cabal-3.14.1.0.md

@@ -0,0 +1,40 @@
+## Cabal and Cabal-syntax 3.14.1.0 changelog
+
+### Significant changes
+
+- Fix build ways for modules in executables [#10418](https://github.com/haskell/cabal/issues/10418) [#10419](https://github.com/haskell/cabal/pull/10419)
+
+  - Modules belonging to executables were being built in too many ways. For instance, if you
+  had configured to build profiled library files then your executable modules would also
+  be built profiled. Which was a regression in behaviour since `Cabal-3.12`.
+
+- Fix ./setup install command [#10416](https://github.com/haskell/cabal/issues/10416) [#10417](https://github.com/haskell/cabal/pull/10417)
+
+  - `./setup install` was failing with a `fromFlag NoFlag` error. It is now fixed.
+
+### Other changes
+
+- Add new options from ghc 9.12 [#10468](https://github.com/haskell/cabal/pull/10468)
+
+  - ghc 9.12 adds several new command line options, divided between
+    `LANGUAGE`s (already added), warnings, new preprocessor control options,
+    and compilation control options. Two options needed to be added to the
+    list of options requiring `Int` parameters.
+
+    The new options, excluding warning and language options, are:
+
+    * `-fexpose-overloaded-unfoldings`
+    * `-fmax-forced-spec-args=N`
+    * `-fno-expose-overloaded-unfoldings`
+    * `-fno-object-determinism`
+    * `-fobject-determinism`
+    * `-fwrite-if-compression=N`
+    * `-optCmmP…`
+    * `-optJSP…`
+    * `-pgmCmmP`
+    * `-pgmJSP`
+
+    As they all affect compilation and store hashes, the only necessary
+    change was to list the two numeric options so they will be parsed
+    correctly. To the best of our understanding, `-pgm*` and `-opt*`
+    options are already handled as a group.

release-notes/cabal-install-3.14.1.0.md

@@ -0,0 +1,16 @@
+## cabal-install and cabal-install-solver 3.14.1.0 changelog
+
+- Fix a bug that causes `cabal init` to crash if `git` is not installed [#8478](https://github.com/haskell/cabal/issues/8478) [#10484](https://github.com/haskell/cabal/issues/10484) [#10486](https://github.com/haskell/cabal/pull/10486)
+
+  - `cabal init` tries to use `git config` to guess the user's name and email.
+    It no longer crashes if there is no executable named `git` on $PATH.
+
+- Print out which project file we are using with the default verbosity [#8519](https://github.com/haskell/cabal/issues/8519) [#10507](https://github.com/haskell/cabal/pull/10507)
+
+  - Many people have been burnt by cabal catching stray project files located up
+    the directory tree. This change tries to protect them at the expense of
+    producing more output by default. In particular, before this change, you could
+    see which project file is in use by supplying `-v` (the verbose mode), and
+    after the change we print this information with the default verbosity.
+    Changing the behaviour of cabal is out of scope of this change, and will
+    hopefully be done in the future versions (see #9353 for a way forward).