Changelogs 3.18.2.0 (#12346)

* Add changelogs for 3.18.2.0

* Remove changelog files for 3.18.2.0

(cherry picked from commit a14e7af)

Author: ffaf1

Cabal/ChangeLog.md

@@ -1,3 +1,6 @@
+# 3.18.2.0 [Francesco Ariis](mailto:fa-ml@ariis.it) September 2026
+* See https://github.com/haskell/cabal/blob/master/release-notes/Cabal-3.18.2.0.md
+
 # 3.18.1.0 [Artem Pelenitsyn](mailto:a@pelenitsyn.top) July 2026
 * See https://github.com/haskell/cabal/blob/master/release-notes/Cabal-3.18.1.0.md
 

changelog.d/10252.md

@@ -0,0 +1,30 @@
+Cabal and Cabal-syntax 3.18.2.0 changelog and release notes
+---
+
+### Significant changes
+
+- Mark `CabalSpecV3_18` as the latest supported specification [#12271](https://github.com/haskell/cabal/issues/12271) [#12273](https://github.com/haskell/cabal/pull/12273)
+
+  `cabalSpecLatest` remained `CabalSpecV3_16` after `CabalSpecV3_18` was
+  introduced. As a result, `cabal-install` treated a `build-type: Simple` package
+  that declared `cabal-version: 3.18` as a future-format package. It then tried to
+  compile an external `Setup.hs` without a Cabal setup dependency, which caused
+  the build to fail.
+
+  `cabalSpecLatest` now points at `CabalSpecV3_18`. Affected packages use the
+  in-process setup path again.
+
+- Fix `renameFileWithRetry` leaving temporary files after copying [#12244](https://github.com/haskell/cabal/issues/12244) [#12246](https://github.com/haskell/cabal/pull/12246)
+
+  `cabal-install build` left a number of temporary (`.tmp` extension)
+  files in the user’s temporary folder (e.g. `/tmp`).  This has been fixed.
+
+### Other changes
+
+- Fix concurrent store creations [#11329](https://github.com/haskell/cabal/issues/11329) [#12114](https://github.com/haskell/cabal/pull/12114)
+
+  Previously, when several cabal processes share one `--store-dir` and that store
+  is cold, they all race `createPackageDBIfMissing`. Precisely hitting the warning
+  above it, noting that it is not thread-safe.
+
+  Fix this by using a fd-based lock, prior to attempting to create the index.

changelog.d/12260.md

@@ -0,0 +1,102 @@
+cabal-install 3.18.2.0 changelog and release notes
+---
+
+### Unresolved issues and Notice
+
+- Cabal package not visible to build auto-generated setup.hs [#11416](https://github.com/haskell/cabal/issues/11416)
+
+    Upgrading from `cabal-install` 3.16.0.0 might give error on autogenerated
+    `Setup.hs`.
+
+    This is fixable by running `cabal build --enable-tests`.
+
+- Putting targets after the argument separator is removed [#12231](https://github.com/haskell/cabal/issues/12231) [#10487](https://github.com/haskell/cabal/pull/10487)
+   Invoking e.g. `cabal run -- target` works no more.  Put the target
+   — and any cabal-specific option — before the hyphen (like this:
+   `cabal run target -- <non-cabal-options>`).
+
+- `cabal-install` works with semaphore version 2 only [#12306](https://github.com/haskell/cabal/issues/12306)
+
+  `cabal-install 3.18` includes support for version 2 of `semaphore-compat`.
+  GHC plans to add support for v2 in releases 9.10.4, 9.12.5, 9.14.2, and
+  10.0.1.
+
+  If those GHCs are not yet released or not available to you, you might
+  consider not updating to `3.18` to keep v1 semaphore working.
+
+- Windows: cannot `cabal install` `cabal-install` [#12269](https://github.com/haskell/cabal/issues/12269)
+
+  This is due to Windows not allowing to delete an open file.
+
+  Workaround: build `cabal-install` and copy it manually to the target
+  folder.
+
+- (Windows) `cabal-install` built in msys-shell links against msys env specific dlls [#12272](https://github.com/haskell/cabal/issue/12272/) [#12274](https://github.com/haskell/cabal/pull/12274/)
+
+    This breaks `cabal-install` on PowerShell if you build the binary
+    with `cabal install cabal-install`.
+
+    Workaround: have an appropriate `cabal.project`. You can simply clone
+    `3.18` and build from there or copy this:
+
+    ```
+    # cabal.project
+    if os(windows)
+      package zlib
+        flags: -pkg-config +bundled-c-zlib
+    ```
+
+### Important changes
+
+- Fix `renameFileWithRetry` leaving temporary files after copying [#12244](https://github.com/haskell/cabal/issues/12244) [#12246](https://github.com/haskell/cabal/pull/12246)
+
+  `cabal-install build` left a number of temporary (`.tmp` extension)
+  files in the user’s temporary folder (e.g. `/tmp`).  This has been fixed.
+
+### Other changes
+
+- Fix cabal upload failure with curl chunked-encoding error [#10252](https://github.com/haskell/cabal/issues/10252) [#12211](https://github.com/haskell/cabal/pull/12211)
+
+  - Removed the newline character from `--write-out` curl arguments when uploading packages. Newer versions of `curl` misinterpret this newline during chunked-encoding transfers, causing upload failures
+
+- Honor `--with-gcc` and program-locations when configuring the compiler [#11881](https://github.com/haskell/cabal/issues/11881) [#12260](https://github.com/haskell/cabal/pull/12260)
+
+  `cabal build` now respects the user-specified locations of toolchain programs
+  such as the C compiler. Previously `--with-gcc` and the `program-locations`
+  section of the config file were ignored, and `cabal` always used the C compiler
+  that GHC was built with. As a result, passing `-pgmc=...` via
+  `program-default-options` did not reliably override the C compiler either.
+
+  The root cause was twofold:
+
+  - When configuring the compiler, the user-supplied program locations were
+    dropped before the toolchain programs (gcc, ar, ld, ...) were re-added.
+  - The elaborated program locations gave the compiler-detected locations
+    precedence over the user-supplied ones.
+
+  Now the user-supplied locations are applied to the compiler's program database
+  and take precedence over auto-detected locations.
+
+- Fix spurious "Unknown field configure-options" warning [#12245](https://github.com/haskell/cabal/issues/12245) [#12276](https://github.com/haskell/cabal/pull/12276)
+
+  The parsec project file parser treated every `-options` field in a `package`
+  stanza as a program option and warned when the program name was unknown. Since
+  `configure`, `test` and `benchmark` are not programs, valid fields like
+  `configure-options` got spuriously flagged as unknown. The warning is now only
+  emitted in `program-options`/`program-locations` stanzas; inside a `package`
+  stanza the field grammar already reports unknown fields.
+
+  ```diff
+    $ cabal build all --dry-run
+  - Warnings found while parsing the project file, cabal.project.local:
+  -  - cabal.project.local:2:3: Unknown field: "configure-options"
+    Build profile: -w ghc-9.12.4 -O1
+  ```
+
+- Fix concurrent store creations [#11329](https://github.com/haskell/cabal/issues/11329) [#12114](https://github.com/haskell/cabal/pull/12114)
+
+  Previously, when several cabal processes share one `--store-dir` and that store
+  is cold, they all race `createPackageDBIfMissing`. Precisely hitting the warning
+  above it, noting that it is not thread-safe.
+
+  Fix this by using a fd-based lock, prior to attempting to create the index.