Bump dune lang version to 2.9

Signed-off-by: Craig Ferguson <me@craigfe.io>

Author: craigfe

doc/dune-files.rst

@@ -12,7 +12,7 @@ contents of all configuration files read by Dune and looks like:
 
 .. code:: scheme
 
-   (lang dune 2.8)
+   (lang dune 2.9)
 
 Additionally, they can contains the following stanzas.
 
@@ -102,7 +102,7 @@ By default, executables defined via ``(executables(s) ...)`` or ``(test(s)
 common to give them empty interface files to strengthen the compiler's ability
 to detect unused values in these modules.
 
-Starting from dune 2.8, an option is available to automatically generate empty
+Starting from dune 2.9, an option is available to automatically generate empty
 interface files for executables and tests that don't already have them:
 
 .. code:: scheme
@@ -651,7 +651,7 @@ binary at the same place as where ``ocamlc`` was found.
 Executables can also be linked as object or shared object files. See
 `linking modes`_ for more information.
 
-Starting from dune 2.8, it's possible to automatically generate empty interface
+Starting from dune 2.9, it's possible to automatically generate empty interface
 files for executables. See `executables_implicit_empty_intf`_.
 
 ``<optional-fields>`` are:
@@ -1365,7 +1365,7 @@ running dune runtest you can use the following stanza:
     (libraries alcotest mylib)
     (action (run %{test} -e)))
 
-Starting from dune 2.8, it's possible to automatically generate empty interface
+Starting from dune 2.9, it's possible to automatically generate empty interface
 files for test executables. See `executables_implicit_empty_intf`_.
 
 test
@@ -1949,7 +1949,7 @@ a typical ``dune-workspace`` file looks like:
 
 .. code:: scheme
 
-    (lang dune 2.8)
+    (lang dune 2.9)
     (context (opam (switch 4.07.1)))
     (context (opam (switch 4.08.1)))
     (context (opam (switch 4.11.1)))
@@ -1961,7 +1961,7 @@ containing exactly:
 
 .. code:: scheme
 
-    (lang dune 2.8)
+    (lang dune 2.9)
     (context default)
 
 This allows you to use an empty ``dune-workspace`` file to mark the root of your

doc/hacking.rst

@@ -172,7 +172,7 @@ Such languages must be enabled in the dune-project separately:
 
 .. code:: scheme
 
-   (lang dune 2.8)
+   (lang dune 2.9)
    (using coq 0.2)
 
 If such extensions are experimental, it's recommended that they pass

doc/instrumentation.rst

@@ -79,14 +79,14 @@ To enable an instrumentation backend globally, you can type in your
 
 .. code:: scheme
 
-   (lang dune 2.8)
+   (lang dune 2.9)
    (instrument_with bisect_ppx)
 
 or for each context individually:
 
 .. code:: scheme
 
-   (lang dune 2.8)
+   (lang dune 2.9)
    (context default)
    (context (default (name coverage) (instrument_with bisect_ppx)))
    (context (default (name profiling) (instrument_with landmarks)))

doc/opam.rst

@@ -94,7 +94,7 @@ configuration will tell ``dune`` to generate two opam files: ``cohttp.opam`` and
 
 .. code:: scheme
 
-   (lang dune 2.8)
+   (lang dune 2.9)
    (name cohttp)
    ; version field is optional
    (version 1.0.0)

doc/sites.rst

@@ -26,7 +26,7 @@ consists of a name and a :ref:`section<install>` (e.g ``lib``, ``share``,
 
 .. code:: scheme
 
-   (lang dune 2.8)
+   (lang dune 2.9)
    (using dune_site 0.1)
    (name mygui)
 
@@ -205,7 +205,7 @@ Main executable (C)
 
 .. code:: scheme
 
-   (lang dune 2.8)
+   (lang dune 2.9)
    (using dune_site 0.1)
    (name c)
    (package
@@ -256,7 +256,7 @@ One plugin (B)
 
 .. code:: scheme
 
-   (lang dune 2.8)
+   (lang dune 2.9)
    (using dune_site 0.1)
    (name b)
 

doc/tests.rst

@@ -479,7 +479,7 @@ with a ``.t`` extension, so they must be enabled manually in the
 
 .. code:: scheme
 
-   (lang dune 2.8)
+   (lang dune 2.9)
    (cram enable)
 
 

src/dune_engine/dune_project.ml

@@ -707,7 +707,7 @@ let parse ~dir ~lang ~opam_packages ~file ~dir_status =
            loc lang.syntax (2, 8) ~what:"This field"
      and+ executables_implicit_empty_intf =
        field_o_b "executables_implicit_empty_intf"
-         ~check:(Dune_lang.Syntax.since Stanza.syntax (2, 8))
+         ~check:(Dune_lang.Syntax.since Stanza.syntax (2, 9))
      and+ () = Dune_lang.Versioned_file.no_more_lang
      and+ generate_opam_files =
        field_o_b "generate_opam_files"

src/dune_engine/stanza.ml

@@ -6,7 +6,7 @@ module Parser = struct
   type nonrec t = string * t list Dune_lang.Decoder.t
 end
 
-let latest_version = (2, 8)
+let latest_version = (2, 9)
 
 let since v = (v, `Since v)
 

test/blackbox-tests/test-cases/dune-ppx-driver-system.t/run.t

@@ -11,7 +11,7 @@ No ppx driver found
   $ dune build --root no-driver
   Entering directory 'no-driver'
   Info: Creating file dune-project with this contents:
-  | (lang dune 2.8)
+  | (lang dune 2.9)
   File "dune", line 5, characters 13-18:
   5 |  (preprocess (pps)))
                    ^^^^^

test/blackbox-tests/test-cases/executables-implicit-empty-intf.t/run.t

@@ -2,7 +2,7 @@ Executables with no corresponding `.mli` file will have one generated for them
 by Dune:
 
   $ cat >dune-project <<EOF
-  > (lang dune 2.8)
+  > (lang dune 2.9)
   > (executables_implicit_empty_intf true)
   > EOF
 
@@ -39,7 +39,7 @@ If an executable already has an interface, it is preserved:
 Generation of empty `.mli` files is disabled by default prior to lang 3.0:
 
   $ dune clean
-  $ echo >dune-project "(lang dune 2.8)"
+  $ echo >dune-project "(lang dune 2.9)"
   $ dune build ./bin/executable.exe
   $ dune runtest
   $ test ! -f _build/default/bin/executable.mli

test/blackbox-tests/test-cases/jsoo/explicit-js-mode-anon.t/run.t

@@ -2,7 +2,7 @@ Anonymous projects have explicit_js_mode enabled
 
   $ dune build --display short @all
   Info: Creating file dune-project with this contents:
-  | (lang dune 2.8)
+  | (lang dune 2.9)
         ocamlc .foo.objs/byte/foo.{cmi,cmo,cmt}
       ocamlopt .foo.objs/native/foo.{cmx,o}
         ocamlc foo.cma

test/blackbox-tests/test-cases/meta-template-version-bug.t

@@ -31,7 +31,7 @@ custom version:
   [1]
 
   $ cat ./_install/lib/foobarlib/dune-package
-  (lang dune 2.8)
+  (lang dune 2.9)
   (use_meta)
 
   $ mkdir external