Users want git tag details (e.g. v1.2.3) and/or the CircleCI release target-version included in build notification emails.

Currently, build notification emails don't surface tag or release version information, making it hard to quickly identify which version of the software a build corresponds to — without clicking through to the CircleCI dashboard.

Use case: When a build is triggered by a tagged commit or a release pipeline, the notification email should include the relevant git tag or target-version so recipients can immediately understand context without leaving their inbox.

Expected behavior: Build notification emails include a "Tag" or "Version" field when the triggering event is a tagged commit or a release, surfacing either:

The git tag (e.g. v2.4.1), or

The CircleCI release target-version