Uploading to CTAN with l3build

A new version of l3build has recently been released with the ability to use curl to automatically upload packages to CTAN.

This functionality has been on our wishlist for some time, with early thoughts around the idea of “reverse engineering” the CTAN upload page like the (now defunct) ctanupload tool by Martin Scharrer. Luckily for us, the CTAN team added an API to allow developers to interface with the CTAN upload process in a well-documented and stable manner.

This API has been used for some time by the ctan-o-mat tool by Gerd Neugebauer, which provides the ability to send package updates through to CTAN via the command line, with metadata for the package loadable via a configuration file. While it’s not a cumbersome process to manually upload packages through CTAN, it’s nice to be able to automate the process.

For a tool like l3build, we prefer not to rely on additional tools beyond a standard TeX distribution, and as Windows now provides a curl utility this has allowed us to build a CTAN-uploading tool into l3build directly. The mechanics of this tool were written by David Carlisle; thanks!

Its use is relatively straightforward. In the package’s build.lua file, add a table along the following lines:

uploadconfig = {
  pkg          = "vertbars",
  version      = "v1.0c",
  author       = "Peter R Wilson; Will Robertson",
  uploader     = "Will Robertson"
  license      = "lppl1.3c",
  summary      = "Mark vertical rules in margin of text",
  ctanPath     = "/macros/latex/contrib/vertbars",
  repository   = "https://github.com/wspr/herries-press/",
  note         = [[Uploaded automatically by l3build...]]
}

Additional fields to what are listed above are possible; this example isn’t intended to be exhaustive. The full list of possibilities is available either through the CTAN API documentation or through the l3build documentation.

Running l3build upload

With the build.lua configuration file in place, to submit a new version of the package to CTAN you would first run l3build ctan to generate the package zip archive, then execute something like

l3build upload --message "Minor update to fix some erroneous spaces from missing % signs"

For a longer message you could use --file releasenotes-v1.0c.txt where the listed filename contains the release notes for this update. Note, however, that there is a fairly small character limit on what can be included here; you may wish to maintain a longer, more detailed, list of changes in a separate CHANGELOG file.

Before the upload process, l3build will check whether any required fields have been omitted and prompt them in an interactive terminal. In particular, the user will be asked their email address for verification purposes; in general this information should not be hard-coded into the build.lua file if that file is to be stored publicly.

Rather than an interactive query, the email field can also be set as a command line option as in

l3build upload --email "my.email@mail.com" ...

Alternatively, you could create a file build-private.lua file in your personal texmf/scripts directory containing

uploadconfig = uploadconfig or {}
uploadconfig.uploader = "My Name"
uploadconfig.email    = "my.name@gmail.com"

And read this into your build.lua file with require('build-private.lua').

Further automation and future plans

The current support does not attempt to automate any aspect of the release process. For instance:

  • You may wish additional logic to check the status of your version control system before proceeding with tagging or upload.
  • You may wish to have l3build tag update the package version automatically.
  • You may wish to populate the announcement field within uploadconfig automatically from an associated CHANGELOG file.

And so on. It’s also worth noting that this tool does not automatically run l3build ctan as that process can be very slow if the test suite needs to be re-run. It is a manual process to run the appropriate tag then ctan then upload steps.

As we gain more experience with how we and others are using the tool we will look into providing more functions around automation and/or convenience, especially integration with version control.

In the mean time, I’m looking forward to having it be a good bit easier to make a quick change to a package and send it through to CTAN.