outdated: accept v1/v2 aliases for freeze-file flags

Cabal/doc/developing-packages.rst

@@ -1333,10 +1333,12 @@ The following flags are supported by the ``outdated`` command:
 ``--freeze-file``
     Read dependency version bounds from the freeze file (``cabal.config``)
     instead of the package description file (``$PACKAGENAME.cabal``).
+    ``--v1-freeze-file`` is an alias for this flag starting in Cabal 2.4.
 ``--new-freeze-file``
     Read dependency version bounds from the new-style freeze file
     (by default, ``cabal.project.freeze``) instead of the package
-    description file.
+    description file. ``--v2-freeze-file`` is an alias for this flag
+    starting in Cabal 2.4.
 ``--project-file`` *PROJECTFILE*
     :since: 2.4
 

cabal-install/Distribution/Client/Setup.hs

@@ -1166,12 +1166,12 @@ outdatedCommand = CommandUI {
     optionVerbosity outdatedVerbosity
       (\v flags -> flags { outdatedVerbosity = v })
 
-    ,option [] ["freeze-file"]
+    ,option [] ["freeze-file", "v1-freeze-file"]
      "Act on the freeze file"
      outdatedFreezeFile (\v flags -> flags { outdatedFreezeFile = v })
      trueArg
 
-    ,option [] ["new-freeze-file"]
+    ,option [] ["new-freeze-file", "v2-freeze-file"]
      "Act on the new-style freeze file (default: cabal.project.freeze)"
      outdatedNewFreezeFile (\v flags -> flags { outdatedNewFreezeFile = v })
      trueArg

cabal-install/changelog

@@ -31,6 +31,8 @@
 	* Add 'v1-' prefixes for the commands that will be replaced in the
 	new-build universe, in preparation for it becoming the default.
 	(#5358)
+	* 'outdated' accepts '--v1-freeze-file' and '--v2-freeze-file'
+	in the same spirit.
 	* Completed the 'new-clean' command (#5357). The functionality is
 	equivalent to old-style clean, but for nix-style builds.
 	* Ensure that each package selected for a build-depends dependency