When `CI_JOB_TOKEN` is used for authentication and `auto-release-enabled`
is `true`, GitLab does not trigger a new pipeline for the release tag
pushed by semantic-release. This was undocumented, causing users to
silently lose their tag pipelines with no explanation.

- Add a warning note to the `CI_JOB_TOKEN` entry in the
  "Supported authentication methods" README section
- Add a cross-reference warning at the tag pipeline description
- Add a runtime `log_warn` in the template script, gated on
  `SEMREL_AUTO_RELEASE_ENABLED=true`, linking to the GitLab docs

Closes #73

fix(docs): auto-release CI_JOB_TOKEN limitation

Closes #73

See merge request !85

## [4.2.2](4.2.1...4.2.2) (2026-05-08)

### Bug Fixes

* **docs:** auto-release CI_JOB_TOKEN limitation ([c9c55a0e](c9c55a0e)), closes [#73](#73)