Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: "lwn" <lwn@lwn.net>, caml-list@inria.fr
Subject: [Caml-list] Attn: Development Editor, Latest OCaml Weekly News
Date: Tue, 10 Nov 2026 12:01:33 +0100	[thread overview]
Message-ID: <m2y0b1hrw2.fsf@mac-03220211.irisa.fr> (raw)


[-- Attachment #1.1.1: Type: text/plain, Size: 32602 bytes --]

Hello

Here is the latest OCaml Weekly News, for the week of November 03 to 10,
2026.

Table of Contents
─────────────────

neocaml 0.11
OSEC-2026-30: OCaml runtime "ephemeron data is freed while still referenced"
OSEC-2026-28: github.com/ocaml/ocaml.org: Unauthenticated arbitrary file read via path traversal in `/conferences/ocaml/**'
OCaml 4.14.5 released
rocq-typescript-extraction (experimental): Extract Rocq definitions to TypeScript ES modules
Bisect_ppx, the coverage tool, moving to ocaml-ppx
Blog post: From AST to CST
Senior OCaml Engineer / Tech Lead – Elpe Open-Source Tool (SuperSafe Project) at OCamlPro
Release of Alcotest 1.10 and dune-release 2.3
Old CWN


neocaml 0.11
════════════

  Archive: <https://discuss.ocaml.org/t/ann-neocaml-0-11/18709/1>


Tim McGilchrist announced
─────────────────────────

  neocaml is a tree-sitter powered Emacs major mode for OCaml. We've
  done major work on adding new functionality and building new
  tree-sitter grammars. @bbatsov posted a nice summary of the work on
  <https://batsov.com/articles/2026/11/05/neocaml-0-11-oxcaml-indentation-styles-and-odoc/>

  Checkout neocaml if you're not already using it. We'd love feedback on
  the new functionality. Thanks


OSEC-2026-30: OCaml runtime "ephemeron data is freed while still referenced"
════════════════════════════════════════════════════════════════════════════

Hannes Mehnert announced
────────────────────────

  Dear everyone,

  a new advisory was published for the OCaml runtime. Below is the
  advisory, you can as well find it at
  <https://github.com/ocaml/security-advisories> and
  <https://osv.dev/list?q=&ecosystem=opam>

  In OCaml 5, this is already fixed.

  Best,

  Hannes

  ┌────
  │ id: OSEC-2026-30
  │ modified:  "2026-11-06T12:30:00Z"
  │ published: "2026-11-06T12:30:00Z"
  │ severity: 
  │ "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N/E:P"
  │ severity_score: "7 (High)"
  │ affected: "ocaml" {< "4.14.5"}
  │ events: [
  │    [
  │      git "https://github.com/ocaml/ocaml" [
  │        [fixed "da301a20833b765e268d677fe693d29fe51793ad"]
  │      ]
  │    ]
  │ ]
  │ credits: [
  │    [reporter "Igor Santos-Grueiro"]
  │    [coordinator "Hannes Mehnert"]
  │    [remediation_reviewer "Florian Angeletti"]
  │    [remediation_developer "Gabriel Scherer"]
  │ ]
  │ cwe: [ CWE-416 ]
  └────

  *Ephemeron data is freed while still referenced when the key is an
  `Infix_tag' closure*


Summary
╌╌╌╌╌╌╌

  In OCaml before 4.14.5, when the key of an ephemeron is a closure with
  `Infix_tag' (a function of a mutually recursive group that is not the
  first function), the mark phase does not keep the ephemeron's data
  alive, although the key is alive. The clean phase does treat the key
  as alive, so it leaves the data field filled. The sweep phase then
  frees the data block. After a major collection the ephemeron's data
  field still points to the freed block.

  This looks like the part of [#7810] that PR [#9742] did not cover. PR
  [#9742] fixed the clean phase and the minor collector. It did not
  change `mark_ephe_aux'.

  Please note that the CVSS score high is under the conditions:
  • /if/ the application is using ephemerons,
  • and /if/ the application is available over the network,
  • and /if/ the attacker can find a way to exploit the memory safety
  issue in an attack chain.


[#7810] <https://github.com/ocaml/ocaml/issues/7810>

[#9742] <https://github.com/ocaml/ocaml/pull/9742>


Reproduction
╌╌╌╌╌╌╌╌╌╌╌╌

  ┌────
  │ [@@@alert "-old_ephemeron_api"]
  │ let infix n = let rec f () = n and g () = f () in g
  │ 
  │ let build key n =
  │    let e = Ephemeron.K1.create () in
  │    let w = Weak.create 1 in
  │    let d = ref n in
  │    Ephemeron.K1.set_key e key;
  │    Ephemeron.K1.set_data e d;
  │    Weak.set w 0 (Some d);
  │    (e, w)
  │ 
  │ let run key =
  │    let (e, w) = build key 1 in
  │    Gc.full_major ();
  │    Printf.printf "tag=%d weak=%b check_key=%b check_data=%b\n"
  │      (Obj.tag (Obj.repr key)) (Weak.check w 0)
  │      (Ephemeron.K1.check_key e) (Ephemeron.K1.check_data e);
  │    ignore (Sys.opaque_identity key)
  │ 
  │ let () =
  │    if Sys.argv.(1) = "infix" then run (infix 1) else run (ref 1)
  └────

  `Obj' is used only to print the tag of the key. The program does not
  read the data after the collection.


Timeline
╌╌╌╌╌╌╌╌

  • 2026-10-04: initial report via email
  • 2026-10-09: develop and committed the fix
  • 2026-11-03: fix was reviewed and merged
  • 2026-11-06: OCaml 4.14.5 released


OSEC-2026-28: github.com/ocaml/ocaml.org: Unauthenticated arbitrary file read via path traversal in `/conferences/ocaml/**'
═══════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════

Hannes Mehnert announced
────────────────────────

  Dear everyone,

  a new advisory was published for the
  <https://github.com/ocaml/ocaml.org> website source code. Below is the
  advisory, you can as well find it at
  <https://github.com/ocaml/security-advisories> and
  <https://osv.dev/list?q=&ecosystem=opam>

  Please note that according to the system administrator, the ocaml.org
  server is run inside a docker container where no secret material is
  present.

  Best,

  Hannes

  ┌────
  │ id: OSEC-2026-28
  │ modified: "2026-11-06T13:30:00Z"
  │ published: "2026-11-06T13:30:00Z"
  │ severity: "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N"
  │ severity_score: "7.5 (High)"
  │ events: [
  │    [
  │      git "https://github.com/ocaml/ocaml.org" [
  │        [fixed "6b08ea625214fddcdd03cf990c004bc2dd77c17a"]
  │      ]
  │    ]
  │ ]
  │ credits: [
  │    [reporter "Sahil Kushwaha"]
  │    [coordinator "Hannes Mehnert"]
  │    [remediation_developer "Cuihtlauac Alvarado"]
  │ ]
  │ cwe: [ CWE-22 ]
  └────

  *Unauthenticated arbitrary file read via path traversal in
  `/conferences/ocaml/**'*

  `GET /conferences/ocaml/<path>' on ocaml.org concatenates the raw
  request target onto `OCAMLORG_V2_PATH' (`/v2') and serves it with
  `Dream.from_filesystem', bypassing the path validation that
  `Dream.static' performs. An unauthenticated request containing `..'
  segments escapes `/v2' and reads arbitrary files as the server
  process, which runs as `root' in the container.

  Please note that the live deployment of <https://ocaml.org> is in a
  dedicated Docker container which does not contain any secrets. Thus
  the vulnerability is in the ocaml.org source code, but there has been
  no impact for the live deployment.


Affected code
╌╌╌╌╌╌╌╌╌╌╌╌╌

  `src/ocamlorg_web/lib/handler.ml:1544 (commit
  ocaml/ocaml.org@31249f2d69fcb243284d3a6a2b91c0a4963f25b5)':

  ┌────
  │ let v2_asset req =
  │    let</>? path =
  │      try Some (Config.v2_path ^ Dream.target req) with _ -> None
  │    in
  │    let</>? () = if Sys.file_exists path then Some () else None in
  │    Filename.(Dream.from_filesystem (dirname path) (basename path) req)
  └────

  The route is public (`src/ocamlorg_web/lib/router.ml:186'):

  ┌────
  │ Dream.get "/conferences/ocaml/**" Handler.v2_asset;
  └────

  `Config.v2_path' is `OCAMLORG_V2_PATH', set to `/v2' in the production
  image (`Dockerfile:68'). `Dream.target' is the request target as
  received; nothing rejects `.' or `..' components.


Timeline
╌╌╌╌╌╌╌╌

  • 2026-10-31 report via <https://github.com/ocaml/security-advisories>
  • 2026-11-02 fixed via <https://github.com/ocaml/ocaml.org/pull/3942>
    and deployed ocaml.org


OCaml 4.14.5 released
═════════════════════

  Archive: <https://discuss.ocaml.org/t/ocaml-4-14-5-released/18733/1>


octachron announced
───────────────────

  We have the pleasure of celebrating the birthdays of Marie
  Skłodowska-Curie and Lise Meitner by announcing the release of OCaml
  version 4.14.5.

  This release is a safe collection of six security fixes, one
  pattern-matching miscompilation fix, and one configuration fix for the
  newest version of macOS. See the full Changes list below.

  If we are using any previous 4.14 version of OCaml, we are advising
  you to switch to this new version.


Evaluating the end of the active maintenance of OCaml 4.14
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  As an important announcement, in January 2027, we will start
  evaluating if it would be reasonable to stop the active maintenance of
  the 4.14 branch between January and June 2027, taking in account that
  maintaining 4.14 is becoming more arduous each passing year.

  If this evaluation does not reveal any major issues, we would stop the
  active maintenance of OCaml 4.14 between June 2027 and the end of
  2027. OCaml 4.14 would still be available, and we would still try to
  keep the branch compatible with newer OSs and C compilers on a best
  effort basis.

  In the meanwhile, do not hesitate to report any bugs on the [OCaml
  issue tracker].

  Happy hacking, Florian Angeletti for the OCaml team.


[OCaml issue tracker] <https://github.com/ocaml/ocaml/issues>


Installation Instructions
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  The base compiler can be installed as an opam switch with the
  following commands:

  opam update opam switch create 4.14.5

  The source code for the release candidate is also directly available
  on:
  • [GitHub]
  • [Inria archive]


[GitHub] <https://github.com/ocaml/ocaml/archive/4.14.5.tar.gz>

[Inria archive]
<https://caml.inria.fr/pub/distrib/ocaml-4.14/ocaml-4.14.5.tar.gz>


Changes in OCaml 4.14.5 (6 November 2026)
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

◊ Bug fixes:

  • [15019], [15030], [OSEC-2026-18]: `Marshal.from_{string,bytes}':
    guard against overflow in the computation of the total data length.
    (Xavier Leroy, report by Akshay Singh, review by Nicolás Ojeda Bär
    and Antonin Décimo)

  • [15113], [OSEC-2026-21]: `Str.string_partial_match': make sure
    captured groups are valid.  (Xavier Leroy, review by Nicolás Ojeda
    Bär and Edwin Török)

  • [15112], [OSEC-2026-22]: `Unix.map_file': protect against overflow
    when computing the data size.  (Xavier Leroy and Nicolás Ojeda Bär,
    review by Nicolás Ojeda Bär and Edwin Török)

  • [15115], [OSEC-2026-23]: Fix multiple issues in demarshaling
    (`Marshal.from_{channel,string,bytes}') (Xavier Leroy, review by
    Nicolás Ojeda Bär)

  • [15133], [OSEC 2026-24]: Multiple issues in command quoting on
    Windows (Xavier Leroy and Nicolás Ojeda Bär, review by Nicolás Ojeda
    Bär)

  • [15233], [OSEC-2026-30]: ensure that ephemeron marking follows Infix
    pointers.  (Gabriel Scherer, review by Florian Angeletti)

  • [15185], [15187]: fix a pattern-matching miscompilation on certain
    combinations of immediate ranges and redundant patterns (Gabriel
    Scherer, report by Alperer Keleş, review by Vincent Laviron and
    Florian Angeletti)

  • [15067], [15071]: Fix detection of functions available in the future
    on macOS.  (Antonin Décimo, review by Nicolás Ojeda Bär and Damien
    Doligez)


  [15019] <https://github.com/ocaml/ocaml/issues/15019>

  [15030] <https://github.com/ocaml/ocaml/issues/15030>

  [OSEC-2026-18] <https://osv.dev/vulnerability/OSEC-2026-18>

  [15113] <https://github.com/ocaml/ocaml/issues/15113>

  [OSEC-2026-21] <https://osv.dev/vulnerability/OSEC-2026-21>

  [15112] <https://github.com/ocaml/ocaml/issues/15112>

  [OSEC-2026-22] <https://osv.dev/vulnerability/OSEC-2026-22>

  [15115] <https://github.com/ocaml/ocaml/issues/15115>

  [OSEC-2026-23] <https://osv.dev/vulnerability/OSEC-2026-23>

  [15133] <https://github.com/ocaml/ocaml/issues/15133>

  [OSEC 2026-24] <https://osv.dev/vulnerability/OSEC-2026-24>

  [15233] <https://github.com/ocaml/ocaml/issues/15233>

  [OSEC-2026-30] <https://osv.dev/vulnerability/OSEC-2026-30>

  [15185] <https://github.com/ocaml/ocaml/issues/15185>

  [15187] <https://github.com/ocaml/ocaml/issues/15187>

  [15067] <https://github.com/ocaml/ocaml/issues/15067>

  [15071] <https://github.com/ocaml/ocaml/issues/15071>


◊ Internal Tools:

  • [11100]: Fix ocamltest to make sure failed tests are not counted as
    "unexpected error".  (Damien Doligez, review by Sébastien Hinderer)


  [11100] <https://github.com/ocaml/ocaml/issues/11100>


rocq-typescript-extraction (experimental): Extract Rocq definitions to TypeScript ES modules
════════════════════════════════════════════════════════════════════════════════════════════

  Archive:
  <https://discuss.ocaml.org/t/ann-rocq-typescript-extraction-experimental-extract-rocq-definitions-to-typescript-es-modules/18734/1>


Sora Morimoto announced
───────────────────────

  I am excited to share an experimental preview of
  *rocq-typescript-extraction*, a Rocq plugin that extracts Rocq
  definitions to TypeScript ES modules.


What is it?
╌╌╌╌╌╌╌╌╌╌╌

  Rocq (formerly Coq) has long supported extraction to OCaml, Haskell,
  and Scheme. This plugin adds a TypeScript backend, generating clean ES
  modules that can be imported and used directly from
  TypeScript/JavaScript code.

  The generated code uses erasable TypeScript syntax (no `namespace',
  `enum', `declare', or type assertions other than `as const') and is
  checked under strict TypeScript settings (`--strict --isolatedModules
  --verbatimModuleSyntax --erasableSyntaxOnly'). It is intended to run
  under Bun or Node with type stripping.


Key capabilities
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  • Inductive types (as discriminated unions with a `tag' property),
    records (as interfaces with `readonly' properties), recursive
    functions, modules, and functors
  • Number and BigInt presets that map standard integers (`nat',
    `positive', `N', `Z') to JavaScript `number' or `bigint'
  • Recursive functions (including many mutually recursive ones) become
    loops with explicit stacks to avoid JavaScript call-stack limits on
    deep inputs
  • Custom extraction directives (`Extract Inductive', `Extract
    Constant', etc.) for mapping to existing TypeScript types or
    implementations
  • Separate extraction (one file per library with relative imports) or
    single-file extraction

  The extraction is designed with performance in mind. The repository
  includes benchmarks (under `bench/') that compare extracted code
  against handwritten JavaScript/TypeScript implementations across a
  range of workloads (sorting, persistent data structures, arithmetic,
  cryptography primitives from fiat-crypto, and more). The goal is that
  the extracted code should not have significant performance issues
  relative to carefully written handwritten equivalents, particularly
  when using the Number preset for values that fit in JavaScript’s safe
  integer range.


◊ Minimal example

  Save this as `Tree.v':

  ┌────
  │ From TypeScriptExtraction Require Import Number.
  │ 
  │ Inductive tree (A : Type) := Leaf | Node (l : tree A) (x : A) (r : tree A).
  │ Arguments Leaf {A}.
  │ Arguments Node {A}.
  │ 
  │ Fixpoint size {A} (t : tree A) : nat :=
  │   match t with Leaf => 0 | Node l _ r => S (size l + size r) end.
  │ 
  │ TypeScript Extraction "tree.ts" size.
  └────

  Compile it:

  ┌────
  │ opam exec -- rocq compile Tree.v
  └────

  Then use the generated module from TypeScript:

  ┌────
  │ import type { Tree } from "./tree.ts";
  │ import { leaf, node, size } from "./tree.ts";
  │ 
  │ const t: Tree<string> = node(leaf, "a", node(leaf, "b", leaf));
  │ size(t); // 2
  └────

  Use `From TypeScriptExtraction Require Import BigInt.' for exact
  `bigint' arithmetic instead of `number'.


◊ Protecting boundaries with Zod

  Because the generated types are ordinary TypeScript interfaces, you
  can pair them with runtime validators such as Zod to enforce
  invariants at untrusted boundaries (JSON, network, user input, etc.).

  Rocq:

  ┌────
  │ From TypeScriptExtraction Require Import Number.
  │ 
  │ Record point := { px : nat; py : nat }.
  │ 
  │ Definition swap (p : point) : point := {| px := py p; py := px p |}.
  │ 
  │ TypeScript Extraction "point.ts" swap.
  └────

  Extracted TypeScript (`point.ts'):

  ┌────
  │ export interface Point {
  │   readonly px: number;
  │   readonly py: number;
  │ }
  │ 
  │ export const swap = (p: Point): Point => ({ px: p.py, py: p.px });
  └────

  Usage with Zod:

  ┌────
  │ import * as z from "zod";
  │ 
  │ import { swap } from "./point";
  │ import type { Point } from "./point";
  │ 
  │ const PointSchema = z.toZod<Point>()(
  │   z
  │     .strictObject({
  │       px: z.number(),
  │       py: z.number(),
  │     })
  │     .readonly()
  │ );
  │ 
  │ const untrustedJson = {
  │   px: 100,
  │   py: 200,
  │ };
  │ 
  │ const point = PointSchema.parse(untrustedJson);
  │ const result = swap(point);
  │ 
  │ console.log(JSON.stringify(untrustedJson, null, 2));
  │ console.log(JSON.stringify(result, null, 2));
  └────

  This keeps the trusted computational core (the extracted `swap')
  separate from boundary validation.

  There is also a short explanatory video demonstrating the workflow
  (defining and proving properties of a state machine in Rocq,
  extracting it, and using the result directly with React’s
  `useReducer') here:

  <https://x.com/smorimoto/status/2118570731990876210>


Limitations & current status (experimental)
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  This is experimental. Please read the limitations carefully in the
  repository documentation before using it in a project:

  • [TypeScript reference] (generated APIs, data representations, and
    limitations)
  • [Extraction guide]


[TypeScript reference]
<https://github.com/smorimoto/rocq-typescript-extraction/blob/main/docs/encoding.md>

[Extraction guide]
<https://github.com/smorimoto/rocq-typescript-extraction/blob/main/docs/extraction.md>


Documentation
╌╌╌╌╌╌╌╌╌╌╌╌╌

  • [README] (quick start)
  • [Extraction guide]
  • [TypeScript reference]
  • [Contributing] (including benchmarks)

  Source: <https://github.com/smorimoto/rocq-typescript-extraction>

  Feedback, bug reports, and contributions are very welcome.


[README] <https://github.com/smorimoto/rocq-typescript-extraction>

[Extraction guide]
<https://github.com/smorimoto/rocq-typescript-extraction/blob/main/docs/extraction.md>

[TypeScript reference]
<https://github.com/smorimoto/rocq-typescript-extraction/blob/main/docs/encoding.md>

[Contributing]
<https://github.com/smorimoto/rocq-typescript-extraction/blob/main/CONTRIBUTING.md>


Bisect_ppx, the coverage tool, moving to ocaml-ppx
══════════════════════════════════════════════════

  Archive:
  <https://discuss.ocaml.org/t/bisect-ppx-the-coverage-tool-moving-to-ocaml-ppx/18752/1>


Anton Bachin announced
──────────────────────

  Dear community!

  Bisect_ppx, the coverage tool, will henceforth be maintained by Nathan
  Rebours and the ocaml-ppx team, and is now moving to the ocaml-ppx org
  at

  <https://github.com/ocaml-ppx/bisect_ppx>

  ocaml-ppx is already the home of ppxlib, Bisect's major dependency,
  and of ocamlformat, which is used throughout Bisect's own test suite
  for normalization; Bisect always needs to stay in sync with both.

  Thank you to the original author of the project, Xavier Clerc; Leonid
  Rozenberg for taking over and maintaining it after Xavier Clerc; and
  all the contributors over the years!

  Happy testing!

  <https://raw.githubusercontent.com/ocaml-ppx/bisect_ppx/master/doc/sample.gif>


Blog post: From AST to CST
══════════════════════════

  Archive:
  <https://discuss.ocaml.org/t/blog-post-from-ast-to-cst/18755/1>


Nicolas Ojeda Bar announced
───────────────────────────

  Dear Community,

  Recently at LexiFi, we re-engineered the parser for a home-grown
  language to produce a CST (concrete syntax tree) rather than an AST
  (abstract syntax tree). The goal was to use the CST as the basis for a
  pretty-printer.

  While I was familiar with the CST approach in principle, I had never
  seen it implemented for a realistic language in practice, so I was not
  entirely sure how well it would work when we started the project.

  Now that the project has turned out to be a success, we've written a
  short blog post to share some of the design choices we made and
  lessons we learned along the way, in the hope that others in the
  community might find it useful.

  <https://www.lexifi.com/blog/ocaml/template-language-cst/>

  Cheers, Nicolas


Senior OCaml Engineer / Tech Lead – Elpe Open-Source Tool (SuperSafe Project) at OCamlPro
═════════════════════════════════════════════════════════════════════════════════════════

  Archive:
  <https://discuss.ocaml.org/t/job-senior-ocaml-engineer-tech-lead-elpe-open-source-tool-supersafe-project-at-ocamlpro/18756/1>


OCamlPro announced
──────────────────

  *Location:* Paris 6ème or Gif-sur-Yvette, up to 2 days/week remote

  *Contract:* Fixed-term 3 years or CDI

  *Salary:* Competitive, based on experience

  At OCamlPro, we are looking for a *Senior OCaml Engineer / Tech Lead*
  to drive the development of *Elpe*, an open-source Nix alternative /
  competitor created by Pierre-Etienne Meunier, to be developed within
  the framework of the European research & innovation project
  *SuperSafe*.

  This is a key technical leadership role running primarily over a
  3-year timeline, combining open-source impact, team coordination,
  developer advocacy, and cross-functional company contributions.


*About the Project: Elpe & SuperSafe*
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  *SuperSafe* is a collaborative European initiative focused on
   high-assurance software security and safety (see
   <https://super-stack.eu/>). Within this consortium, *Elpe* is an
   open-source tool designed to replace Nix and NixPkgs within security
   sensitive projects. The source code is written in Rust (for the
   server) and OCaml (for the client) and is available here:
   <https://nest.pijul.com/pmeunier/elpe/tree> . Within the SuperSafe
   project, our goal is to transform the current prototype of Elpe into
   a robust, portable and powerful tool, to build a community of users
   and contributors in Europe, and to develop OCamlPro's commercial
   offering around Elpe.

  You will lead the technical vision and hands-on implementation of Elpe
  according to the European project roadmap, collaborating closely with
  external partners across Europe as well as an internal project manager
  and several engineers at OCamlPro.


*What You Will Do*
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  • *Lead Elpe’s Development (~60–70%):*
    ‣ Steer technical architecture, code quality, and release cycles for
      Elpe.
    ‣ Mentor and coordinate a team of developers (internal engineers and
      external open-source contributors).
    ‣ Work closely with the dedicated Project Manager to align
      milestones and deliverables with the European SuperSafe
      consortium.
  • *Community Advocacy & Evangelism (~10–15%):*
    ‣ Represent the project at major open-source and developer
      conferences (e.g., FOSDEM, Open Source Experience / OSXP, Cyber
      events, etc.).
    ‣ Engage with the broader software safety and security communities
      (writing blog posts, RFCs, documentation, answering issues).
  • *Internal Company Contributions (~15–20%):*
    ‣ Bridge R&D work with our commercial and product teams (providing
      technical expertise for pre-sales, RFPs, or product demos).
    ‣ Contribute to OCamlPro’s general technical roadmap and
      cross-cutting engineering initiatives.


*What We Are Looking For*
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  • *Strong OCaml and Rust Experience:* Significant real-world
     experience building robust, maintainable systems or developer
     tooling in OCaml, and a working knowledge of Rust.
  • *Technical Leadership:* Experience leading code reviews,
     architecting complex codebases, and mentoring junior/mid-level
     engineers.
  • *Open-Source Mindset:* Familiarity with modern version control
     workflows (Git/GitLab/GitHub, and interest in Pijul) and open
     source practices (CI/CD, issue triage, RFC processes,
     documentation).
  • *Communication & Collaboration:*
    ‣ Fluent English (written and spoken) for consortium meetings and
      public speaking at conferences.
    ‣ Fluent French (written and spoken) for collaboration within
      OCamlPro.
    ‣ Ability to translate deep technical concepts to non-technical
      stakeholders (sales team, clients, project partners).
  • *Bonus Points:*
    ‣ Hands-on familiarity with Nix, Nixpkgs, Guix, or build systems /
      package managers in general.
    ‣ Background in static analysis, formal methods, compiler design, or
      security tooling.
    ‣ Prior experience working on EU-funded research projects (Horizon
      Europe, etc.).
    ‣ Active involvement in the OCaml ecosystem (opam packages, compiler
      contributions, or tooling).


*What We Offer*
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  • Direct impact on a strategic, high-visibility open-source European
    initiative.
  • A supportive engineering culture valuing correctness, typed
    functional programming, and open standards.
  • Budget and travel support for conferences (FOSDEM, OSXP, etc.).


*How to Apply*
╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  Please send your resume, along with a link to your GitHub/GitLab
  profile or recent OCaml/Rust projects, to *contact@ocamlpro.com* with
  the subject [Senior OCaml Lead - Elpe].

  Feel free to reach out via DM here on Discuss if you have any
  questions before applying!


Release of Alcotest 1.10 and dune-release 2.3
═════════════════════════════════════════════

  Archive:
  <https://discuss.ocaml.org/t/ann-release-of-alcotest-1-10-and-dune-release-2-3/18763/1>


Thomas Gazagnaire announced
───────────────────────────

  Hi everyone,

  I'm happy to announce the (about to be) release of `alcotest 1.10.0'
  and `dune-release 2.3.0'. Those two releases contain years of backlog
  for those two projects, so I'm pretty excited they are finally going
  out!

  You can use them by doing:

  ┌────
  │ opam install dune-release.2.3.0
  │ 
  │ # https://github.com/ocaml/opam-repository/pull/31135
  │ opam pin add alcotest.1.10.0 --dev
  └────

  I am particularly thankful for the [24 alcotest contributors] and [13
  dune-release contributors] listed on the respective release pages.

  Here are a few highlights:

  • /dune-release/ now works on Windows (well… at least `distrib' and
    `check' now work and are tested in the CI) finishing the work
    @emillon started in 2021 and follows `.gitattributes' exclusions
    when generating release archives (thanks to @jjb)!
  • /alcotest/ finally got a few highly-requested features;
    • a bunch of combinators to write tests: `suite', `test' and …
      `group'! Yes *nested tests are now possible* without a breaking
      API change (from @CraigFe's initial RFC, with API inputs from
      @yawaramin and @mjambon);
    • every failing test now prints the file and line of your test
      (inspired by @dbuenzli's [B0_testing]);
    • test suites can now carry tags (that can be filtered on the
      command-line), extending the pre-existing `quick' / `slow'
      arbitrary distinction (also from @CraigFe's RFC, but the final
      implementation and API is quite different to remain backward
      compatible) ;
    • a new opt-in mode to generate JUnit XML files, from unmodified
      test suites (just set `ALCOTEST_JUNIT=1' in your CI environment)
      (inspired by @Khady's [junit_alcotest] idea) ;
    • and wasm_of_ocaml support (from @hhugo and @mefyl)

  There are a few breaking changes: Alcotest now requires at least OCaml
  4.14 and code that extend (like plugins) but for most users the change
  should be fairly transparent. Any weird breakage is a bug! Please
  report those!

  Read more (including an example on how to use tags and JUnit reports
  to work better with flaky tests) on [my blog].


[24 alcotest contributors]
<https://github.com/mirage/alcotest/releases/tag/1.10.0>

[13 dune-release contributors]
<https://github.com/tarides/dune-release/releases/tag/2.3.0>

[B0_testing]
<https://erratique.ch/software/b0/doc/B0_testing/index.html>

[junit_alcotest] <https://github.com/Khady/ocaml-junit>

[my blog]
<https://gazagnaire.org/blog/2026-11-09-alcotest-dune-release.html>


Old CWN
═══════

  If you happen to miss a CWN, you can [send me a message] and I'll mail
  it to you, or go take a look at [the archive] or the [RSS feed of the
  archives].

  If you also wish to receive it every week by mail, you may subscribe
  to the [caml-list].

  [Alan Schmitt]


[send me a message] <mailto:alan.schmitt@polytechnique.org>

[the archive] <https://alan.petitepomme.net/cwn/>

[RSS feed of the archives] <https://alan.petitepomme.net/cwn/cwn.rss>

[caml-list] <https://sympa.inria.fr/sympa/info/caml-list>

[Alan Schmitt] <https://alan.petitepomme.net/>


[-- Attachment #1.1.2: Type: text/html, Size: 53232 bytes --]

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 568 bytes --]

             reply	other threads:[~2026-11-10 11:01 UTC|newest]

Thread overview: 318+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-10 11:01 Alan Schmitt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-11-03 11:03 Alan Schmitt
2026-10-27 10:29 Alan Schmitt
2026-10-20  8:16 alan.schmitt
2026-10-13  6:57 Alan Schmitt
2026-10-06 13:15 Alan Schmitt
2026-09-29  7:10 Alan Schmitt
2026-09-22  7:41 Alan Schmitt
2026-09-15  8:08 Alan Schmitt
2026-09-08 13:20 Alan Schmitt
2026-09-01  9:14 Alan Schmitt
2026-08-25  7:36 Alan Schmitt
2026-08-18  6:56 Alan Schmitt
2026-08-11 12:25 Alan Schmitt
2026-08-04  7:44 Alan Schmitt
2026-07-28 12:44 Alan Schmitt
2026-07-21 16:02 Alan Schmitt
2026-07-14  7:16 Alan Schmitt
2026-07-07 13:29 Alan Schmitt
2026-06-30 13:25 Alan Schmitt
2026-06-23 10:07 Alan Schmitt
2026-06-16 10:51 Alan Schmitt
2026-06-09  7:39 Alan Schmitt
2026-06-02  9:01 Alan Schmitt
2026-05-26  7:36 Alan Schmitt
2026-05-19  8:52 Alan Schmitt
2026-05-12  7:28 Alan Schmitt
2026-05-05  9:35 Alan Schmitt
2026-04-28  7:59 Alan Schmitt
2026-04-21  9:34 Alan Schmitt
2026-04-14  9:50 Alan Schmitt
2026-04-07  9:32 Alan Schmitt
2026-03-31  6:10 Alan Schmitt
2026-03-24  9:58 Alan Schmitt
2026-03-17 14:39 Alan Schmitt
2026-03-10 13:30 Alan Schmitt
2026-03-03 13:54 Alan Schmitt
2026-02-24 13:36 Alan Schmitt
2026-02-17 13:47 Alan Schmitt
2026-02-10 10:36 Alan Schmitt
2026-02-03 10:04 Alan Schmitt
2026-01-27 12:41 Alan Schmitt
2026-01-20  9:19 Alan Schmitt
2026-01-13  8:27 Alan Schmitt
2026-01-06 13:14 Alan Schmitt
2025-12-30  9:33 Alan Schmitt
2025-12-23 11:00 Alan Schmitt
2025-12-16 13:30 Alan Schmitt
2025-12-09 15:04 Alan Schmitt
2025-12-02 10:39 Alan Schmitt
2025-11-25 13:49 Alan Schmitt
2025-11-18 14:01 Alan Schmitt
2025-11-11  9:49 Alan Schmitt
2025-11-04 13:21 Alan Schmitt
2025-10-28 13:30 Alan Schmitt
2025-10-21  9:17 Alan Schmitt
2025-10-14  9:56 Alan Schmitt
2025-10-07 12:22 Alan Schmitt
2025-09-30 13:12 Alan Schmitt
2025-09-23 13:23 Alan Schmitt
2025-09-16 11:52 Alan Schmitt
2025-09-09 12:30 Alan Schmitt
2025-09-02 12:23 Alan Schmitt
2025-08-26 12:34 Alan Schmitt
2025-08-19 12:20 Alan Schmitt
2025-08-12 15:32 Alan Schmitt
2025-08-05  8:17 Alan Schmitt
2025-07-29  9:36 Alan Schmitt
2025-07-22 12:07 Alan Schmitt
2025-07-15 17:14 Alan Schmitt
2025-07-08 12:45 Alan Schmitt
2025-07-01 11:16 Alan Schmitt
2025-06-24 14:02 Alan Schmitt
2025-06-17  6:44 Alan Schmitt
2025-06-10 13:36 Alan Schmitt
2025-06-03  9:19 Alan Schmitt
2025-05-27  9:22 Alan Schmitt
2025-05-20 11:52 Alan Schmitt
2025-05-13  9:40 Alan Schmitt
2025-05-06  7:24 Alan Schmitt
2025-04-29  8:39 Alan Schmitt
2025-04-22 11:50 Alan Schmitt
2025-04-15  9:51 Alan Schmitt
2025-04-08 13:14 Alan Schmitt
2025-04-01  9:12 Alan Schmitt
2025-03-25  8:06 Alan Schmitt
2025-03-18 10:18 Alan Schmitt
2025-03-11 15:00 Alan Schmitt
2025-03-04 14:01 Alan Schmitt
2025-02-25 10:36 Alan Schmitt
2025-02-18 14:33 Alan Schmitt
2025-02-11  7:17 Alan Schmitt
2025-02-04 12:05 Alan Schmitt
2025-01-28 13:24 Alan Schmitt
2025-01-21 15:47 Alan Schmitt
2025-01-14  8:20 Alan Schmitt
2025-01-07 17:26 Alan Schmitt
2024-12-31  8:03 Alan Schmitt
2024-12-24  8:55 Alan Schmitt
2024-12-17 13:05 Alan Schmitt
2024-12-10 13:48 Alan Schmitt
2024-12-03 14:44 Alan Schmitt
2024-11-26  8:30 Alan Schmitt
2024-11-19  6:52 Alan Schmitt
2024-11-12 15:00 Alan Schmitt
2024-11-05 13:22 Alan Schmitt
2024-10-29 13:30 Alan Schmitt
2024-10-22 12:42 Alan Schmitt
2024-10-15 13:31 Alan Schmitt
2024-10-08 10:56 Alan Schmitt
2024-10-01 13:37 Alan Schmitt
2024-09-24 13:18 Alan Schmitt
2024-09-17 14:02 Alan Schmitt
2024-09-10 13:55 Alan Schmitt
2024-09-03  8:24 Alan Schmitt
2024-08-27  9:02 Alan Schmitt
2024-08-20  9:29 Alan Schmitt
2024-08-13 13:21 Alan Schmitt
2024-08-06  9:00 Alan Schmitt
2024-07-30 13:26 Alan Schmitt
2024-07-23 13:30 Alan Schmitt
2024-07-16  6:24 Alan Schmitt
2024-07-09  9:19 Alan Schmitt
2024-07-02  7:30 Alan Schmitt
2024-06-25 13:58 Alan Schmitt
2024-06-18 13:05 Alan Schmitt
2024-06-11 15:04 Alan Schmitt
2024-06-04 13:26 Alan Schmitt
2024-05-28  9:07 Alan Schmitt
2024-05-21 13:07 Alan Schmitt
2024-05-14 13:25 Alan Schmitt
2024-05-07  7:30 Alan Schmitt
2024-04-30  7:22 Alan Schmitt
2024-04-23 12:17 Alan Schmitt
2024-04-16 12:00 Alan Schmitt
2024-04-09  9:15 Alan Schmitt
2024-04-02 14:31 Alan Schmitt
2024-03-26  6:32 Alan Schmitt
2024-03-19 15:09 Alan Schmitt
2024-03-12 10:31 Alan Schmitt
2024-03-05 14:50 Alan Schmitt
2024-02-27 13:53 Alan Schmitt
2024-02-20  9:12 Alan Schmitt
2024-02-13  8:42 Alan Schmitt
2024-02-06 15:14 Alan Schmitt
2024-01-30 14:16 Alan Schmitt
2024-01-23  9:45 Alan Schmitt
2024-01-16 10:01 Alan Schmitt
2024-01-09 13:40 Alan Schmitt
2024-01-02  8:59 Alan Schmitt
2023-12-26 10:12 Alan Schmitt
2023-12-19 10:10 Alan Schmitt
2023-12-12 10:20 Alan Schmitt
2023-12-05 10:13 Alan Schmitt
2023-11-28  9:09 Alan Schmitt
2023-11-21  7:47 Alan Schmitt
2023-11-14 13:42 Alan Schmitt
2023-11-07 10:31 Alan Schmitt
2023-10-31 10:43 Alan Schmitt
2023-10-24  9:17 Alan Schmitt
2023-10-17  7:46 Alan Schmitt
2023-10-10  7:48 Alan Schmitt
2023-10-03 13:00 Alan Schmitt
2023-09-19  8:54 Alan Schmitt
2023-09-12 13:21 Alan Schmitt
2023-09-05  9:00 Alan Schmitt
2023-08-29 13:04 Alan Schmitt
2023-08-22  9:20 Alan Schmitt
2023-08-15 16:33 Alan Schmitt
2023-08-08  8:53 Alan Schmitt
2023-08-01  7:13 Alan Schmitt
2023-07-25  8:45 Alan Schmitt
2023-07-11  8:45 Alan Schmitt
2023-07-04  9:18 Alan Schmitt
2023-06-27  8:38 Alan Schmitt
2023-06-20  9:52 Alan Schmitt
2023-06-13  7:09 Alan Schmitt
2023-06-06 14:22 Alan Schmitt
2023-05-30 15:43 Alan Schmitt
2023-05-23  9:41 Alan Schmitt
2023-05-16 13:05 Alan Schmitt
2023-05-09 11:49 Alan Schmitt
2023-05-02  8:01 Alan Schmitt
2023-04-25  9:25 Alan Schmitt
2023-04-18  8:50 Alan Schmitt
2023-04-11 12:41 Alan Schmitt
2023-04-04  8:45 Alan Schmitt
2023-03-28  7:21 Alan Schmitt
2023-03-21 10:07 Alan Schmitt
2023-03-14  9:52 Alan Schmitt
2023-03-07  9:02 Alan Schmitt
2023-02-28 14:38 Alan Schmitt
2023-02-21 10:19 Alan Schmitt
2023-02-14  8:12 Alan Schmitt
2023-02-07  8:16 Alan Schmitt
2023-01-31  6:44 Alan Schmitt
2023-01-24  8:57 Alan Schmitt
2023-01-17  8:37 Alan Schmitt
2022-11-29 14:53 Alan Schmitt
2022-09-27  7:17 Alan Schmitt
2022-09-20 14:01 Alan Schmitt
2022-09-13  8:40 Alan Schmitt
2022-08-23  8:06 Alan Schmitt
2022-08-16  8:51 Alan Schmitt
2022-08-09  8:02 Alan Schmitt
2022-08-02  9:51 Alan Schmitt
2022-07-26 17:54 Alan Schmitt
2022-07-19  8:58 Alan Schmitt
2022-07-12  7:59 Alan Schmitt
2022-07-05  7:42 Alan Schmitt
2022-06-28  7:37 Alan Schmitt
2022-06-21  8:06 Alan Schmitt
2022-06-14  9:29 Alan Schmitt
2022-06-07 10:15 Alan Schmitt
2022-05-31 12:29 Alan Schmitt
2022-05-24  8:04 Alan Schmitt
2022-05-17  7:12 Alan Schmitt
2022-05-10 12:30 Alan Schmitt
2022-05-03  9:11 Alan Schmitt
2022-04-26  6:44 Alan Schmitt
2022-04-19  5:34 Alan Schmitt
2022-04-12  8:10 Alan Schmitt
2022-04-05 11:50 Alan Schmitt
2022-03-29  7:42 Alan Schmitt
2022-03-22 13:01 Alan Schmitt
2022-03-15  9:59 Alan Schmitt
2022-03-01 13:54 Alan Schmitt
2022-02-22 12:43 Alan Schmitt
2022-02-08 13:16 Alan Schmitt
2022-02-01 13:00 Alan Schmitt
2022-01-25 12:44 Alan Schmitt
2022-01-11  8:20 Alan Schmitt
2022-01-04  7:56 Alan Schmitt
2021-12-28  8:59 Alan Schmitt
2021-12-21  9:11 Alan Schmitt
2021-12-14 11:02 Alan Schmitt
2021-11-30 10:51 Alan Schmitt
2021-11-16  8:41 Alan Schmitt
2021-11-09 10:08 Alan Schmitt
2021-11-02  8:50 Alan Schmitt
2021-10-19  8:23 Alan Schmitt
2021-09-28  6:37 Alan Schmitt
2021-09-21  9:09 Alan Schmitt
2021-09-07 13:23 Alan Schmitt
2021-08-24 13:44 Alan Schmitt
2021-08-17  6:24 Alan Schmitt
2021-08-10 16:47 Alan Schmitt
2021-07-27  8:54 Alan Schmitt
2021-07-20 12:58 Alan Schmitt
2021-07-06 12:33 Alan Schmitt
2021-06-29 12:24 Alan Schmitt
2021-06-22  9:04 Alan Schmitt
2021-06-01  9:23 Alan Schmitt
2021-05-25  7:30 Alan Schmitt
2021-05-11 14:47 Alan Schmitt
2021-05-04  8:57 Alan Schmitt
2021-04-27 14:26 Alan Schmitt
2021-04-20  9:07 Alan Schmitt
2021-04-06  9:42 Alan Schmitt
2021-03-30 14:55 Alan Schmitt
2021-03-23  9:05 Alan Schmitt
2021-03-16 10:31 Alan Schmitt
2021-03-09 10:58 Alan Schmitt
2021-02-23  9:51 Alan Schmitt
2021-02-16 13:53 Alan Schmitt
2021-02-02 13:56 Alan Schmitt
2021-01-26 13:25 Alan Schmitt
2021-01-19 14:28 Alan Schmitt
2021-01-12  9:47 Alan Schmitt
2021-01-05 11:22 Alan Schmitt
2020-12-29  9:59 Alan Schmitt
2020-12-22  8:48 Alan Schmitt
2020-12-15  9:51 Alan Schmitt
2020-12-01  8:54 Alan Schmitt
2020-11-03 15:15 Alan Schmitt
2020-10-27  8:43 Alan Schmitt
2020-10-20  8:15 Alan Schmitt
2020-10-06  7:22 Alan Schmitt
2020-09-29  7:02 Alan Schmitt
2020-09-22  7:27 Alan Schmitt
2020-09-08 13:11 Alan Schmitt
2020-09-01  7:55 Alan Schmitt
2020-08-18  7:25 Alan Schmitt
2020-07-28 16:57 Alan Schmitt
2020-07-21 14:42 Alan Schmitt
2020-07-14  9:54 Alan Schmitt
2020-07-07 10:04 Alan Schmitt
2020-06-30  7:00 Alan Schmitt
2020-06-16  8:36 Alan Schmitt
2020-06-09  8:28 Alan Schmitt
2020-05-19  9:52 Alan Schmitt
2020-05-12  7:45 Alan Schmitt
2020-05-05  7:45 Alan Schmitt
2020-04-28 12:44 Alan Schmitt
2020-04-21  8:58 Alan Schmitt
2020-04-14  7:28 Alan Schmitt
2020-04-07  7:51 Alan Schmitt
2020-03-31  9:54 Alan Schmitt
2020-03-24  9:31 Alan Schmitt
2020-03-17 11:04 Alan Schmitt
2020-03-10 14:28 Alan Schmitt
2020-03-03  8:00 Alan Schmitt
2020-02-25  8:51 Alan Schmitt
2020-02-18  8:18 Alan Schmitt
2020-02-04  8:47 Alan Schmitt
2020-01-28 10:53 Alan Schmitt
2020-01-21 14:08 Alan Schmitt
2020-01-14 14:16 Alan Schmitt
2020-01-07 13:43 Alan Schmitt
2019-12-31  9:18 Alan Schmitt
2019-12-17  8:52 Alan Schmitt
2019-12-10  8:21 Alan Schmitt
2019-12-03 15:42 Alan Schmitt
2019-11-26  8:33 Alan Schmitt
2019-11-12 13:21 Alan Schmitt
2019-11-05  6:55 Alan Schmitt
2019-10-15  7:28 Alan Schmitt
2019-09-03  7:35 Alan Schmitt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2y0b1hrw2.fsf@mac-03220211.irisa.fr \
    --to=alan.schmitt@polytechnique.org \
    --cc=caml-list@inria.fr \
    --cc=lwn@lwn.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox