Create a release or tagger

Prepare and create a release tag for version 2.4.0 across the repository. Use annotated tags with the release notes I pasted into the commit, sign the tag with the release key, and push the tag to origin. Then create the corresponding release entry in our releases page with the changelog and link to the CI artifact. Confirm the tag exists remotely and that CI artifacts are attached.

Before I publish this release tag to the repo, make it easier for the release reviewer to approve: put the key version number and top three user-facing fixes at the top, show where the release artifacts are stored, and flag any commits in the range that touch migrations or config files. Call out any missing signed tag or missing release notes and suggest wording to close those gaps.

I made an annotated tag for 2.4.0 and pushed, but the release page shows no artifacts and the CI didn't pick up the tag. I do not know whether the tag was lightweight by mistake, whether the CI only triggers on branches, or whether my push lacked the signed tag. Which diagnosis is most likely and what exact command or minimal change should I run now to create a proper annotated, signed tag and get CI to pick up the release artifacts?

We repeatedly create tags for releases that lack proper notes, signatures, or attached artifacts, and then redo the release which confuses customers. What habit and checklist should the release owner adopt so every tag is annotated, signed, and has CI artifacts before it's pushed? Offer a short pre-push checklist and a one-line commit message convention to enforce over the next three releases.