>_ IzzyLab

Hands-on task

This task is step 4 of the course “Shipping a release”

Annotated release tag

easy~12 min

/root/billing is a clone of the billing repository from GitLab (the web sign-in is on the GitLab tab). The latest commit in main bumps the version to 2.4.0 — that's the one we're releasing.

  1. Put an annotated tag v2.4.0 with the message Release 2.4.0 on this commit and push the tag to GitLab. An annotated tag is a separate object in git with an author, a date and a message, and releases need exactly that. The previous release is marked with a lightweight tag v2.3.7 — just a name for a commit, with no message.
  2. Create a release for this tag in GitLab: Deploy → Releases → Create a new release. In the tag field, pick the existing v2.4.0; the title and description are up to you.
What you'll practise:
  • git tag -a
  • annotated tags
  • releases
  • GitLab Releases
  • git push

Topic breakdown

A tag is a permanent name for a commit, and releases use annotated tags: an annotated tag is a separate object in the git database with an author, a date and a message, it can be signed, and git describe relies on such tags by default. A lightweight tag is just a pointer to a hash with no metadata, fine for personal markers. The kind is set by git tag flags, and git cat-file -t checks what you got: an annotated tag gives tag, a lightweight one goes straight to commit.

What's checked

  1. annotated tag v2.4.0 in GitLab
  2. tag message is Release 2.4.0
  3. the tag is on the commit with version 2.4.0
  4. release v2.4.0 is published in GitLab

What it looks like