GitHub Action
Set up OCaml
STATUS: STABLE
Set up an OCaml and opam environment in GitHub Actions and add to PATH.
Consult the Hello World OCaml Action that uses Dune and opam to build a simple library.
It's possible to feed different values to the input depending on the platform of the runner. The syntax of GitHub's workflows is flexible enough to offer several methods to do this.
name: Builds, tests & co
on:
pull_request:
push:
schedule:
# Prime the caches every Monday
- cron: 0 1 * * MON
permissions: read-all
jobs:
build:
strategy:
fail-fast: false
matrix:
os:
- macos-latest
- ubuntu-latest
- windows-latest
ocaml-compiler:
- "5.1"
runs-on: ${{ matrix.os }}
steps:
- name: Checkout tree
uses: actions/checkout@v4
- name: Set-up OCaml ${{ matrix.ocaml-compiler }}
uses: ocaml/setup-ocaml@v2
with:
ocaml-compiler: ${{ matrix.ocaml-compiler }}
- run: opam install . --deps-only --with-test
- run: opam exec -- dune build
- run: opam exec -- dune runtest
The actions are downloaded and run from the GitHub graph of repositories. The workflow references an action using a ref.
Note Binding to a major version is the latest of that major version (e.g.
v2
=2.*
)Major versions should guarantee compatibility. A major version can add net new capabilities but should not break existing input compatibility or break existing workflows.
- name: Set-up OCaml ${{ matrix.ocaml-compiler }}
uses: ocaml/setup-ocaml@v2
# ^^^
with:
ocaml-compiler: ${{ matrix.ocaml-compiler }}
Warning do not reference
master
since that is the latest code and can be carrying breaking changes of the next major version.
Major version binding allows you to take advantage of bug fixes, critical functionality and security fixes. The master
branch has the latest code and is unstable to bind to since changes get committed to the master
and released by creating a tag.
steps:
# Reference the major version of a release (most recommended)
- uses: ocaml/setup-ocaml@v2
# Reference a specific commit (most strict)
- uses: ocaml/setup-ocaml@<SHA>
# Reference a semver version of a release (not recommended)
- uses: ocaml/[email protected]
# Reference a branch (most dangerous - do not do this)
- uses: ocaml/setup-ocaml@master
Name | Required | Description | Type | Default |
---|---|---|---|---|
ocaml-compiler |
Yes | The OCaml compiler packages to initialise. Consult the supported version syntax section. | string | |
opam-repositories |
No | The name and URL pair of the repository to fetch the packages from. | string | |
opam-pin |
No | Enable the automation feature for opam pin. | bool | true |
opam-depext |
No | Enable the automation feature for opam depext. | bool | true |
opam-depext-flags |
No | The flags for the opam depext command. The flags must be separated by the comma. | string | |
opam-local-packages |
No | The local packages to be used by opam-pin or opam-depext . Consult the @actions/glob documentation package for supported patterns. |
string | *.opam |
opam-disable-sandboxing |
No | Disable the opam sandboxing feature. | bool | false |
dune-cache |
No | Enable the dune cache feature. This feature requires dune 2.8.5 or later on the Windows runners. | bool | false |
cache-prefix |
No | The prefix of the cache keys. | string | v1 |
The ocaml-compiler
input supports the Semantic Versioning Specification, for more detailed examples please refer to the documentation.
Note With the naughty exception of
4.02.2
, point releases are meant to be strictly compatible, so once we (OCaml dev team) release a new point release, upgrading should be a no-brainer.
Examples:
- Exact package name:
ocaml-base-compiler.5.1.0
,ocaml-variants.4.14.0+mingw64c
- Combine multiple packages:
ocaml-variants.5.1.0+options,ocaml-option-flambda,ocaml-option-musl,ocaml-option-static
- Minor versions:
4.08
,4.14
,5.1
,5.1.x
- More specific versions:
~4.02.2
,5.1.0
,
Consult the examples page for more complex patterns.
STATUS: EXPERIMENTAL
Note: All extends are recommended to be used in separate jobs run on ubuntu-latest
.
Consult the Configuring Dependabot version updates page and set .github/dependabot.yml
as described below to allow Dependabot to update the actions automatically.
version: 2
updates:
- package-ecosystem: github-actions
directory: /
schedule:
interval: weekly
Note Renovate is also available for free as a third-party tool, which is much more flexible than Dependabot - depending on the project and your preferences. If you just want to automate GitHub Actions updates, Dependabot is good enough.
This action aims to provide an OS-neutral interface to opam
, and so will not add features that only work on one operating system. It will also track the latest stable release of opam.
Please feel free to post to the discuss.ocaml.org forum with any questions you have about this action.
Previous discussions include: