Skip to content

Commit

Permalink
release 4.14.0
Browse files Browse the repository at this point in the history
  • Loading branch information
Octachron committed Mar 28, 2022
1 parent 54c6b3f commit 15553b7
Show file tree
Hide file tree
Showing 6 changed files with 25 additions and 25 deletions.
2 changes: 1 addition & 1 deletion VERSION
@@ -1,4 +1,4 @@
4.14.0+dev13-2022-03-28
4.14.0

# Starting with OCaml 4.14, although the version string that appears above is
# still correct and this file can thus still be used to figure it out,
Expand Down
Binary file modified boot/ocamlc
Binary file not shown.
Binary file modified boot/ocamllex
Binary file not shown.
4 changes: 2 additions & 2 deletions build-aux/ocaml_version.m4
Expand Up @@ -25,7 +25,7 @@
# The following macro, OCAML__DEVELOPMENT_VERSION, should be either
# [true] of [false].

m4_define([OCAML__DEVELOPMENT_VERSION], [true])
m4_define([OCAML__DEVELOPMENT_VERSION], [false])

# The three following components (major, minor and patch level) MUST be
# integers. They MUST NOT be left-padded with zeros and all of them,
Expand All @@ -36,7 +36,7 @@ m4_define([OCAML__VERSION_MINOR], [14])
m4_define([OCAML__VERSION_PATCHLEVEL], [0])
# Note that the OCAML__VERSION_EXTRA string defined below is always empty
# for officially-released versions of OCaml.
m4_define([OCAML__VERSION_EXTRA], [dev13-2022-03-28])
m4_define([OCAML__VERSION_EXTRA], [])

# The OCAML__VERSION_EXTRA_PREFIX macro defined below should be a
# single character:
Expand Down
40 changes: 20 additions & 20 deletions configure

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

4 changes: 2 additions & 2 deletions ocaml-variants.opam
@@ -1,7 +1,7 @@
opam-version: "2.0"
version: "4.14.0+trunk"
version: "4.14.0"
license: "LGPL-2.1-or-later WITH OCaml-LGPL-linking-exception"
synopsis: "OCaml development version"
synopsis: "Official release of OCaml 4.14.0"
depends: [
"ocaml" {= "4.14.0" & post}
"base-unix" {post}
Expand Down

0 comments on commit 15553b7

Please sign in to comment.