diff --git a/CHANGES.md b/CHANGES.md
--- a/CHANGES.md
+++ b/CHANGES.md
@@ -22,11 +22,17 @@
 See also the hledger changelog.
 
 
-# 2025-03-07 1.42
+# 2025-03-12 1.42.1
 
+- Build with hledger 1.42.1.
+
+
+# 1.42 2025-03-07
+
 Fixes
 
-- Fix a test suite build issue: -threaded is needed in test suite now also.
+- Fix a test suite build issue: build it with -threaded.
+
 
 # 1.41 2024-12-09
 
diff --git a/hledger-web.1 b/hledger-web.1
--- a/hledger-web.1
+++ b/hledger-web.1
@@ -1,5 +1,5 @@
 
-.TH "HLEDGER\-WEB" "1" "March 2025" "hledger-web-1.42 " "hledger User Manuals"
+.TH "HLEDGER\-WEB" "1" "March 2025" "hledger-web-1.42.1 " "hledger User Manuals"
 
 
 
@@ -17,7 +17,7 @@
 .PD
 \f[CR]hledger web \-\- [OPTS] [QUERY]\f[R]
 .SH DESCRIPTION
-This manual is for hledger\[aq]s web interface, version 1.42.
+This manual is for hledger\[aq]s web interface, version 1.42.1.
 See also the hledger manual for common concepts and file formats.
 .PP
 hledger is a robust, user\-friendly, cross\-platform set of programs for
diff --git a/hledger-web.cabal b/hledger-web.cabal
--- a/hledger-web.cabal
+++ b/hledger-web.cabal
@@ -5,7 +5,7 @@
 -- see: https://github.com/sol/hpack
 
 name:           hledger-web
-version:        1.42
+version:        1.42.1
 synopsis:       Web user interface for the hledger accounting system
 description:    A simple web user interface for the hledger accounting system,
                 providing a more modern UI than the command-line or terminal interfaces.
@@ -156,7 +156,7 @@
   hs-source-dirs:
       ./
   ghc-options: -Wall -Wredundant-constraints -Wincomplete-record-updates -Wincomplete-uni-patterns
-  cpp-options: -DVERSION="1.42"
+  cpp-options: -DVERSION="1.42.1"
   build-depends:
       Decimal >=0.5.1
     , aeson >=1 && <2.3
@@ -178,8 +178,8 @@
     , filepath
     , githash >=0.1.6.2
     , hjsmin
-    , hledger ==1.42.*
-    , hledger-lib ==1.42.*
+    , hledger >=1.42.1 && <1.43
+    , hledger-lib >=1.42.1 && <1.43
     , hspec
     , http-client
     , http-conduit
@@ -224,7 +224,7 @@
   hs-source-dirs:
       app
   ghc-options: -Wall -Wredundant-constraints -Wincomplete-record-updates -Wincomplete-uni-patterns -with-rtsopts=-T
-  cpp-options: -DVERSION="1.42"
+  cpp-options: -DVERSION="1.42.1"
   build-depends:
       base >=4.14 && <4.21
     , base-compat >=0.14.0
@@ -247,7 +247,7 @@
   hs-source-dirs:
       test
   ghc-options: -Wall -Wredundant-constraints -Wincomplete-record-updates -Wincomplete-uni-patterns
-  cpp-options: -DVERSION="1.42"
+  cpp-options: -DVERSION="1.42.1"
   build-depends:
       base >=4.14 && <4.21
     , base-compat >=0.14.0
diff --git a/hledger-web.info b/hledger-web.info
--- a/hledger-web.info
+++ b/hledger-web.info
@@ -18,7 +18,7 @@
 or
 'hledger web -- [OPTS] [QUERY]'
 
-   This manual is for hledger's web interface, version 1.42.  See also
+   This manual is for hledger's web interface, version 1.42.1.  See also
 the hledger manual for common concepts and file formats.
 
    hledger is a robust, user-friendly, cross-platform set of programs
@@ -529,15 +529,15 @@
 
 Tag Table:
 Node: Top223
-Node: OPTIONS2566
-Node: PERMISSIONS11255
-Node: EDITING UPLOADING DOWNLOADING12606
-Node: RELOADING13621
-Node: JSON API14188
-Node: DEBUG OUTPUT19837
-Node: Debug output19989
-Node: ENVIRONMENT20507
-Node: BUGS20743
+Node: OPTIONS2568
+Node: PERMISSIONS11257
+Node: EDITING UPLOADING DOWNLOADING12608
+Node: RELOADING13623
+Node: JSON API14190
+Node: DEBUG OUTPUT19839
+Node: Debug output19991
+Node: ENVIRONMENT20509
+Node: BUGS20745
 
 End Tag Table
 
diff --git a/hledger-web.txt b/hledger-web.txt
--- a/hledger-web.txt
+++ b/hledger-web.txt
@@ -11,41 +11,41 @@
        hledger web -- [OPTS] [QUERY]
 
 DESCRIPTION
-       This manual is for hledger's web interface, version 1.42.  See also the
-       hledger manual for common concepts and file formats.
+       This manual is for hledger's web interface, version 1.42.1.   See  also
+       the hledger manual for common concepts and file formats.
 
-       hledger is a robust, user-friendly, cross-platform set of programs  for
-       tracking  money,  time,  or any other commodity, using double-entry ac-
-       counting and a simple, editable file format.  hledger  is  inspired  by
-       and  largely  compatible  with  ledger(1), and largely interconvertible
+       hledger  is a robust, user-friendly, cross-platform set of programs for
+       tracking money, time, or any other commodity,  using  double-entry  ac-
+       counting  and  a  simple, editable file format.  hledger is inspired by
+       and largely compatible with  ledger(1),  and  largely  interconvertible
        with beancount(1).
 
-       hledger-web is a simple web application for browsing and adding  trans-
-       actions.   It  provides a more user-friendly UI than the hledger CLI or
-       hledger-ui TUI, showing more at once  (accounts,  the  current  account
+       hledger-web  is a simple web application for browsing and adding trans-
+       actions.  It provides a more user-friendly UI than the hledger  CLI  or
+       hledger-ui  TUI,  showing  more  at once (accounts, the current account
        register, balance charts) and allowing history-aware data entry, inter-
        active searching, and bookmarking.
 
-       hledger-web  also lets you share a journal with multiple users, or even
-       the public web.  There is no access control, so if you  need  that  you
-       should  put  it  behind  a  suitable  web proxy.  As a small protection
-       against data loss when running an unprotected  instance,  it  writes  a
+       hledger-web also lets you share a journal with multiple users, or  even
+       the  public  web.   There is no access control, so if you need that you
+       should put it behind a suitable  web  proxy.   As  a  small  protection
+       against  data  loss  when  running an unprotected instance, it writes a
        numbered backup of the main journal file (only) on every edit.
 
-       Like  hledger,  it reads from (and appends to) a journal file specified
-       by   the    LEDGER_FILE    environment    variable    (defaulting    to
-       $HOME/.hledger.journal);  or you can specify files with -f options.  It
-       can also read timeclock files, timedot files, or any  CSV/SSV/TSV  file
+       Like hledger, it reads from (and appends to) a journal  file  specified
+       by    the    LEDGER_FILE    environment    variable    (defaulting   to
+       $HOME/.hledger.journal); or you can specify files with -f options.   It
+       can  also  read timeclock files, timedot files, or any CSV/SSV/TSV file
        with a date field.  (See hledger(1) -> Input for details.)
 
        hledger-web can be run in three modes:
 
        o Transient mode (the default): your default web browser will be opened
-         to  show  the  app if possible, and the app exits automatically after
-         two minutes of inactivity (no requests received and no  open  browser
+         to show the app if possible, and the app  exits  automatically  after
+         two  minutes  of inactivity (no requests received and no open browser
          windows viewing it).
 
-       o With  --serve:  the  app runs without stopping, and without opening a
+       o With --serve: the app runs without stopping, and  without  opening  a
          browser.
 
        o With --serve-api: only the JSON API is served.
@@ -76,28 +76,28 @@
                                           runner args may follow a --, eg: hledger-web --test
                                           -- --help
 
-       By default hledger-web listens only on IP address 127.0.0.1,  which  be
+       By  default  hledger-web listens only on IP address 127.0.0.1, which be
        accessed only from the local machine.
 
        To allow access from elsewhere, use --host to specify an externally ac-
-       cessible  address  configured  on  this  machine,  The  special address
+       cessible address  configured  on  this  machine,  The  special  address
        0.0.0.0 causes it to listen on all of this machine's addresses.
 
-       Similarly, you can use --port to listen on a TCP port other than  5000.
-       This  is  useful if you want to run multiple hledger-web instances on a
+       Similarly,  you can use --port to listen on a TCP port other than 5000.
+       This is useful if you want to run multiple hledger-web instances  on  a
        machine.
 
-       When --socket is used,  hledger-web  creates  and  communicates  via  a
-       socket  file  instead of a TCP port.  This can be more secure, respects
+       When  --socket  is  used,  hledger-web  creates  and communicates via a
+       socket file instead of a TCP port.  This can be more  secure,  respects
        unix file permissions, and makes certain use cases easier, such as run-
        ning per-user instances behind an nginx reverse proxy.  (Eg: proxy_pass
        http://unix:/tmp/hledger/${remote_user}.socket;.)
 
-       You can use --base-url to change the protocol, hostname, port and  path
-       that  appear in hledger-web's hyperlinks.  This is useful eg when inte-
-       grating  hledger-web  within  a  larger  website.    The   default   is
-       http://HOST:PORT/  using  the  server's configured host address and TCP
-       port (or http://HOST if PORT is 80).  Note this affects url  generation
+       You  can use --base-url to change the protocol, hostname, port and path
+       that appear in hledger-web's hyperlinks.  This is useful eg when  inte-
+       grating   hledger-web   within   a  larger  website.   The  default  is
+       http://HOST:PORT/ using the server's configured host  address  and  TCP
+       port  (or http://HOST if PORT is 80).  Note this affects url generation
        but not route parsing.
 
        hledger-web also supports many of hledger's general options:
@@ -183,29 +183,29 @@
                    --pager=YN             use a pager when needed ? y/yes (default) or n/no
                    --color=YNA --colour   use ANSI color ? y/yes, n/no, or auto (default)
 
-       hledger-web   shows  accounts  with  zero  balances  by  default  (like
-       hledger-ui, and unlike hledger).  Using the -E/--empty  flag  will  re-
-       verse  this behaviour.  If you see accounts which appear to have a zero
-       balance, but cannot be  hidden  with  -E,  it's  because  they  have  a
-       mixed-cost  balance,  which  looks  like  zero  when  costs are hidden.
+       hledger-web  shows  accounts  with  zero  balances  by  default   (like
+       hledger-ui,  and  unlike  hledger).  Using the -E/--empty flag will re-
+       verse this behaviour.  If you see accounts which appear to have a  zero
+       balance,  but  cannot  be  hidden  with  -E,  it's  because they have a
+       mixed-cost balance, which  looks  like  zero  when  costs  are  hidden.
        (hledger-web does not show costs.)
 
-       Reporting options and/or query arguments can be used to set an  initial
+       Reporting  options and/or query arguments can be used to set an initial
        query, which although not shown in the UI, will restrict the data shown
        (in addition to any search query entered in the UI).
 
-       If  you use the bash shell, you can auto-complete flags by pressing TAB
-       in the command line.  If this is not working see Install >  Shell  com-
+       If you use the bash shell, you can auto-complete flags by pressing  TAB
+       in  the  command line.  If this is not working see Install > Shell com-
        pletions.
 
 PERMISSIONS
-       By  default,  hledger-web  allows  anyone  who can reach it to view the
+       By default, hledger-web allows anyone who can  reach  it  to  view  the
        journal and to add new transactions, but not to change existing data.
 
        You can restrict who can reach it by
 
-       o setting the IP address it listens on (see --host above).  By  default
-         it  listens  on  127.0.0.1,  accessible to all users on the local ma-
+       o setting  the IP address it listens on (see --host above).  By default
+         it listens on 127.0.0.1, accessible to all users  on  the  local  ma-
          chine.
 
        o putting it behind an authenticating proxy, using eg apache or nginx
@@ -215,44 +215,44 @@
        You can restrict what the users who reach it can do, by
 
        o using the --capabilities=CAP[,CAP..] flag when you start it, enabling
-         one or more of the following  capabilities.   The  default  value  is
+         one  or  more  of  the  following capabilities.  The default value is
          view,add:
 
          o view - allows viewing the journal file and all included files
 
          o add - allows adding new transactions to the main journal file
 
-         o manage  -  allows editing, uploading or downloading the main or in-
+         o manage - allows editing, uploading or downloading the main  or  in-
            cluded files
 
-       o using the --capabilities-header=HTTPHEADER flag  to  specify  a  HTTP
-         header  from  which it will read capabilities to enable.  hledger-web
-         on Sandstorm uses the  X-Sandstorm-Permissions  header  to  integrate
+       o using  the  --capabilities-header=HTTPHEADER  flag  to specify a HTTP
+         header from which it will read capabilities to  enable.   hledger-web
+         on  Sandstorm  uses  the  X-Sandstorm-Permissions header to integrate
          with Sandstorm's permissions.  This is disabled by default.
 
 EDITING, UPLOADING, DOWNLOADING
-       If  you  enable the manage capability mentioned above, you'll see a new
-       "spanner" button to the right of the search form.  Clicking  this  will
-       let  you edit, upload, or download the journal file or any files it in-
+       If you enable the manage capability mentioned above, you'll see  a  new
+       "spanner"  button  to the right of the search form.  Clicking this will
+       let you edit, upload, or download the journal file or any files it  in-
        cludes.
 
-       Note, unlike any other hledger command, in this mode you (or any  visi-
+       Note,  unlike any other hledger command, in this mode you (or any visi-
        tor) can alter or wipe the data files.
 
-       Normally  whenever  a  file is changed in this way, hledger-web saves a
-       numbered backup (assuming file permissions allow it, the  disk  is  not
-       full,  etc.)  hledger-web is not aware of version control systems, cur-
-       rently; if you use one, you'll have to arrange to  commit  the  changes
+       Normally whenever a file is changed in this way,  hledger-web  saves  a
+       numbered  backup  (assuming  file permissions allow it, the disk is not
+       full, etc.)  hledger-web is not aware of version control systems,  cur-
+       rently;  if  you  use one, you'll have to arrange to commit the changes
        yourself (eg with a cron job or a file watcher like entr).
 
-       Changes  which would leave the journal file(s) unparseable or non-valid
-       (eg with failing balance assertions) are prevented.   (Probably.   This
+       Changes which would leave the journal file(s) unparseable or  non-valid
+       (eg  with  failing balance assertions) are prevented.  (Probably.  This
        needs re-testing.)
 
 RELOADING
        hledger-web detects changes made to the files by other means (eg if you
-       edit  it  directly,  outside  of hledger-web), and it will show the new
-       data when you reload the page or navigate to a new page.  If  a  change
+       edit it directly, outside of hledger-web), and it  will  show  the  new
+       data  when  you reload the page or navigate to a new page.  If a change
        makes a file unparseable, hledger-web will display an error message un-
        til the file has been fixed.
 
@@ -260,8 +260,8 @@
        that both machine clocks are roughly in step.)
 
 JSON API
-       In  addition to the web UI, hledger-web also serves a JSON API that can
-       be used to get data or add new transactions.  If you want the JSON  API
+       In addition to the web UI, hledger-web also serves a JSON API that  can
+       be  used to get data or add new transactions.  If you want the JSON API
        only, you can use the --serve-api flag.  Eg:
 
               $ hledger-web -f examples/sample.journal --serve-api
@@ -278,7 +278,7 @@
               /accounttransactions/ACCOUNTNAME
 
        Eg, all account names in the journal (similar to the accounts command).
-       (hledger-web's  JSON  does  not include newlines, here we use python to
+       (hledger-web's JSON does not include newlines, here we  use  python  to
        prettify it):
 
               $ curl -s http://127.0.0.1:5000/accountnames | python -m json.tool
@@ -319,26 +319,26 @@
                                       "aprice": null,
               ...
 
-       Most of the JSON corresponds to hledger's data types;  for  details  of
-       what  the fields mean, see the Hledger.Data.Json haddock docs and click
-       on the various data types, eg Transaction.  And for a higher level  un-
+       Most  of  the  JSON corresponds to hledger's data types; for details of
+       what the fields mean, see the Hledger.Data.Json haddock docs and  click
+       on  the various data types, eg Transaction.  And for a higher level un-
        derstanding, see the journal docs.  There is also a basic OpenAPI spec-
        ification.
 
        In some cases there is outer JSON corresponding to a "Report" type.  To
-       understand  that,  go to the Hledger.Web.Handler.MiscR haddock and look
-       at the source for the appropriate handler to see what it  returns.   Eg
+       understand that, go to the Hledger.Web.Handler.MiscR haddock  and  look
+       at  the  source for the appropriate handler to see what it returns.  Eg
        for /accounttransactions it's getAccounttransactionsR, returning a "ac-
-       countTransactionsReport  ...".   Looking up the haddock for that we can
-       see that  /accounttransactions  returns  an  AccountTransactionsReport,
-       which  consists  of a report title and a list of AccountTransactionsRe-
+       countTransactionsReport ...".  Looking up the haddock for that  we  can
+       see  that  /accounttransactions  returns  an AccountTransactionsReport,
+       which consists of a report title and a list  of  AccountTransactionsRe-
        portItem (etc).
 
-       You can add a new transaction to the journal  with  a  PUT  request  to
-       /add,  if  hledger-web  was started with the add capability (enabled by
+       You  can  add  a  new  transaction to the journal with a PUT request to
+       /add, if hledger-web was started with the add  capability  (enabled  by
        default).  The payload must be the full, exact JSON representation of a
-       hledger transaction (partial data won't do).  You can get  sample  JSON
-       from  hledger-web's  /transactions  or /accounttransactions, or you can
+       hledger  transaction  (partial data won't do).  You can get sample JSON
+       from hledger-web's /transactions or /accounttransactions,  or  you  can
        export it with hledger-lib, eg like so:
 
               .../hledger$ stack ghci hledger-lib
@@ -434,28 +434,28 @@
                   "tstatus": "Unmarked"
               }
 
-       And here's how to test adding it with curl.  This should add a new  en-
+       And  here's how to test adding it with curl.  This should add a new en-
        try to your journal:
 
               $ curl http://127.0.0.1:5000/add -X PUT -H 'Content-Type: application/json' --data-binary @txn.json
 
 DEBUG OUTPUT
    Debug output
-       You  can  add  --debug[=N]  to the command line to log debug output.  N
+       You can add --debug[=N] to the command line to  log  debug  output.   N
        ranges from 1 (least output, the default) to 9 (maximum output).  Typi-
-       cally you would start with 1 and increase until you are seeing  enough.
-       Debug  output  goes  to stderr, interleaved with the requests logged on
+       cally  you would start with 1 and increase until you are seeing enough.
+       Debug output goes to stderr, interleaved with the  requests  logged  on
        stdout.  To capture debug output in a log file instead, you can usually
        redirect stderr, eg:
        hledger-web --debug=3 2>hledger-web.log.
 
 ENVIRONMENT
-       LEDGER_FILE The main journal  file  to  use  when  not  specified  with
+       LEDGER_FILE  The  main  journal  file  to  use  when not specified with
        -f/--file.  Default: $HOME/.hledger.journal.
 
 BUGS
        We  welcome  bug  reports  in  the  hledger  issue  tracker  (shortcut:
-       https://bugs.hledger.org),  or  on  the  hledger  chat  or  mail   list
+       https://bugs.hledger.org),   or  on  the  hledger  chat  or  mail  list
        (https://hledger.org/support).
 
        Some known issues:
@@ -480,4 +480,4 @@
 SEE ALSO
        hledger(1), hledger-ui(1), hledger-web(1), ledger(1)
 
-hledger-web-1.42                  March 2025                    HLEDGER-WEB(1)
+hledger-web-1.42.1                March 2025                    HLEDGER-WEB(1)
