A Github action to release Clojure tools.deps projects to clojars.

It creates a new release on clojars, where the version is the name of your tag. It can also create snapshot releases on every push, in this case, the version will be ${BRANCH_NAME}-SNAPSHOT.

A minimal pom.xml is expected in the project root, e.g.:

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
  <modelVersion>4.0.0</modelVersion>
  <groupId>${GROUP_ID}</groupId>
  <artifactId>${ARTIFACT_ID}</artifactId>
  <version>LATEST</version>
  <name>${PROJECT_NAME}</name>
  <description>A description</description>
  <url>https://github.com/$USER/$PROJECT</url>

  <licenses>
    <license>
      <name>Eclipse Public License</name>
      <url>http://www.eclipse.org/legal/epl-v10.html</url>
    </license>
  </licenses>

  <developers>
    <developer>
      <name>Your name</name>
    </developer>
  </developers>

  <scm>
    <url>https://github.com/$USER/$PROJECT</url>
    <connection>scm:git:git://github.com/$USER/$PROJECT.git</connection>
    <developerConnection>scm:git:ssh://git@github.com/$USER/$PROJECT.git</developerConnection>
    <tag>HEAD</tag>
  </scm>

</project>

Notice that your pom.xml is used as a template, you don't need to define your dependencies nor your source directory, since that data will be generated from your deps.edn (via clojure -Spom).

Also, version and smc/tag values don't matter, since they will be replaced with the data from git (tag or branch name).

Required Your clojars username

Required Your clojars token. As of 2020-06-27, Clojars will no longer accept your Clojars password, you have to use a token instead. Read more about this here: Clojars wiki: Deploy Tokens

To learn about about GitHub secrets, see Creating and storing encrypted secrets on GitHub help

The release version is extracted from the git tag/branch. If you don't like this behavior and you prefer to manage the version number manually, set USE_GIT_REF to false. The version number will be taken unmodified from your pom.xml file.

.github/workflows/release.yaml:

on:
  push:
    branches:
      - master
    tags:
      - "*"

jobs:
  clojars:
    runs-on: ubuntu-latest

    steps:
      # This step checks out a copy of your repository.
      - uses: actions/checkout@v2

      - uses: jlesquembre/clojars-publish-action@0.3
        env:
          CLOJARS_USERNAME: ${{ secrets.CLOJARS_USERNAME }}
          CLOJARS_PASSWORD: ${{ secrets.CLOJARS_PASSWORD }}

Git should be the only source of truth for versioning. Git is widely adopted and Git objects are immutable. It doesn't make sense to keep the version number in a file if you already have that information in Git.

Every time you create a new Git tag, this action will create a new release on clojars with the tag's name.

For convenience, every time you push to a branch, a new SNAPSHOT version is created, based on the branch name. For example, if you push to dev branch, a new release dev-SNAPSHOT will be created. That approach makes more sense because:

• It makes clearer what version you are getting from the SNAPSHOT. For example, if you are working on branches foo and bar for the next release, what version will you get from 1.0.1-SNAPSHOT? foo or bar? You don't know, it depends on the latest push.
• You can't be sure about your next version number. Maybe you are thinking about releasing 1.0.1, but in the end, some breaking changes are needed and you need to release version 2.0.0.
• It is useless to have that many SNAPSHOT versions. Many projects have 1.0.1-SNAPSHOT, 1.0.2-SNAPSHOT, 1.0.3-SNAPSHOT, and so on. But after the next release, who cares about previous snapshots? If 1.1.0 was released, who cares about 1.0.X-SNAPSHOT?

Keep in mind that in Clojure projects, you can use Git coordinates for dependencies, prefer it to snapshots.