v2.7.3

.github/ISSUE_TEMPLATE/bug_report.md

@@ -5,7 +5,7 @@ about: Report a bug in Stack
 
 Please follow the steps below for reporting a bug:
 
-Make sure that you are using the latest release (currently stack-2.7.1).
+Make sure that you are using the latest release (currently stack-2.7.3).
 See the [upgrade instructions](http://docs.haskellstack.org/en/stable/install_and_upgrade/#upgrade) to upgrade.
 
 Please use the following schema for your bug report:

.github/ISSUE_TEMPLATE/feature_request.md

@@ -3,7 +3,7 @@ name: Feature Request
 about: Request a feature be added to Stack, or discuss such a feature
 ---
 
-Make sure that you are using the latest release (currently stack-2.7.1).
+Make sure that you are using the latest release (currently stack-2.7.3).
 See the [upgrade instructions](http://docs.haskellstack.org/en/stable/install_and_upgrade/#upgrade) to upgrade.
 
 Please state as clearly as possible what feature you are recommending,

ChangeLog.md

@@ -1,19 +1,14 @@
 # Changelog
 
 
-## Unreleased changes
-
-Release notes:
+## v2.7.3
 
 **Changes since v2.7.1:**
 
-Major changes:
-
-Behavior changes:
-
 Other enhancements:
 
-* `stack upgrade` will download from `haskellstack.org` before trying `github.com`. See
+* `stack upgrade` will download from `haskellstack.org` before trying
+  `github.com`. See
   [#5288](https://github.com/commercialhaskell/stack/issues/5288)
 * `stack upgrade` makes less assumptions about archive format. See
   [#5288](https://github.com/commercialhaskell/stack/issues/5288)
@@ -30,12 +25,14 @@ Bug fixes:
   [pantry#33](https://github.com/commercialhaskell/pantry/issues/33)
 * When building the sanity check for a new GHC install, make sure to clear
   `GHC_PACKAGE_PATH`.
-* Specifying GHC RTS flags in the `stack.yaml` no longer fails with an error. [#5568](https://github.com/commercialhaskell/stack/pull/5568)
+* Specifying GHC RTS flags in the `stack.yaml` no longer fails with an error.
+  [#5568](https://github.com/commercialhaskell/stack/pull/5568)
 * `stack setup` will look in sandboxed directories for executables, not
   relying on `findExecutables. See
   [GHC issue 20074](https://gitlab.haskell.org/ghc/ghc/-/issues/20074)
-* Track changes to `setup-config` properly to avoid reconfiguring on every change.
-  See [#5578](https://github.com/commercialhaskell/stack/issues/5578)
+* Track changes to `setup-config` properly to avoid reconfiguring on every
+  change. See [#5578](https://github.com/commercialhaskell/stack/issues/5578)
+
 
 ## v2.7.1
 

doc/GUIDE.md

@@ -450,7 +450,7 @@ With that out of the way, let's dig a little bit more into these package sets,
 also known as *snapshots*. We mentioned the LTS resolvers, and you can get quite a bit of
 information about it at [https://www.stackage.org/lts](https://www.stackage.org/lts), including:
 
-* The appropriate resolver value (`resolver: lts-17.9`, as is currently the latest LTS)
+* The appropriate resolver value (`resolver: lts-18.3`, as is currently the latest LTS)
 * The GHC version used
 * A full list of all packages available in this snapshot
 * The ability to perform a Hoogle search on the packages in this snapshot
@@ -467,7 +467,7 @@ default as well).
 
 ## Resolvers and changing your compiler version
 
-Let's explore package sets a bit further. Instead of lts-17.9, let's change our
+Let's explore package sets a bit further. Instead of lts-18.3, let's change our
 `stack.yaml` file to use [the latest nightly](https://www.stackage.org/nightly). Right now,
 this is currently 2020-03-24 - please see the resolve from the link above to get the latest.
 
@@ -483,8 +483,8 @@ We can also change resolvers on the command line, which can be useful in a
 Continuous Integration (CI) setting, like on Travis. For example:
 
 ```
-michael@d30748af6d3d:~/helloworld$ stack --resolver lts-17.9 build
-Downloaded lts-17.9 build plan.
+michael@d30748af6d3d:~/helloworld$ stack --resolver lts-18.3 build
+Downloaded lts-18.3 build plan.
 # build output ...
 ```
 
@@ -1143,7 +1143,7 @@ follows the Unix convention of `--` to separate these, e.g.:
 ```
 michael@d30748af6d3d:~$ stack exec --package stm -- echo I installed the stm package via --package stm
 Run from outside a project, using implicit global project config
-Using latest snapshot resolver: lts-17.9
+Using latest snapshot resolver: lts-18.3
 Writing global (non-project-specific) config file to: /home/michael/.stack/global/stack.yaml
 Note: You can change the snapshot via the resolver field there.
 I installed the stm package via --package stm

etc/dockerfiles/arm64.Dockerfile

@@ -30,4 +30,4 @@ USER stack
 RUN cd /src && stack build --only-snapshot --test && stack build shake
 
 COPY etc/scripts/release.hs /src
-RUN stack script --resolver lts-17.10 --compile /src/release.hs -- --version && cp /src/release /home/stack
+RUN stack script --resolver lts-17.15 --compile /src/release.hs -- --version && cp /src/release /home/stack

package.yaml

@@ -1,5 +1,5 @@
 name: stack
-version: '2.8.0'
+version: '2.7.3'
 synopsis: The Haskell Tool Stack
 description: |
   Please see the documentation at <https://docs.haskellstack.org>

stack.cabal

@@ -1,13 +1,13 @@
 cabal-version: 2.0
 
--- This file has been generated from package.yaml by hpack version 0.33.0.
+-- This file has been generated from package.yaml by hpack version 0.34.4.
 --
 -- see: https://github.com/sol/hpack
 --
--- hash: 4d6bc382d1f25fc7283e144b701061b38a5f10879c44997cfdc0b9f3147ce352
+-- hash: a602fe627b6dcb4f50470060f0b90cf1ee668145c6332918e48247480bb1bf8b
 
 name:           stack
-version:        2.8.0
+version:        2.7.3
 synopsis:       The Haskell Tool Stack
 description:    Please see the documentation at <https://docs.haskellstack.org>
                 for usage information.

stack.yaml

@@ -1,4 +1,4 @@
-resolver: lts-17.10
+resolver: lts-17.15
 
 packages:
 - .
@@ -20,9 +20,6 @@ flags:
 ghc-options:
    "$locals": -fhide-source-paths
 
-extra-deps:
-- pantry-0.5.2@rev:0
-
 drop-packages:
 # See https://github.com/commercialhaskell/stack/pull/4712
 - cabal-install