Point the go-unittests component at the purpose-built go-unittest image
from common-ci-tasks-images!1691 instead of the stock golang image, and
drop the runtime `go install` of gotestsum and gocover-cobertura.

Those tools are now baked into the image at pinned versions (gotestsum
1.13.0, gocover-cobertura 1.5.0) and already on PATH, which speeds up the
job and removes the non-deterministic `@latest` installs. This mirrors
the existing golangci-lint and goreleaser components.

Consumers adopt it automatically when Renovate bumps their component pin;
no repo changes are required.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Verification jobs (lint/format/validate/test) re-ran in tag-triggered
pipelines via the parent_pipeline rule, even though that work already ran
on the branch before the tag was created.

Add a reusable `notTagged` rule atom and bake it into the shared
verification builders (standard/linterRules/mrOnly) so verification jobs
are consistently skipped when $CI_COMMIT_TAG is set. Build jobs whose
artifacts feed downstream tag-pipeline jobs (nix-build, cargo-build) and
the tube resolver opt back in via `allowTags=true`.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

feat: run go-unittests on the pre-baked go-unittest image

See merge request !1810

## [5.5.0](https://gitlab.com/gitlab-com/gl-infra/common-ci-tasks/-/compare/...) (2026-08-27)

### Features

* run go-unittests on the pre-baked go-unittest image ([0b0a93ef](0b0a93ef))

fix(rules): skip verification jobs in tag pipelines

See merge request !1814

## [5.5.1](https://gitlab.com/gitlab-com/gl-infra/common-ci-tasks/-/compare/...) (2026-08-27)

### Fixes

* **rules:** skip verification jobs in tag pipelines ([730e7fff](730e7fff))

chore(deps): update dependency gitlab-org/labkit to v2.37.0

See merge request !1815

merge-train-deactivate ran the deactivation PUT whenever the branches
were converged. On a release with no unreleased security fix, activation
never runs take_ownership, so the schedule is still owned by the
provisioning bot and the PUT gets a 403. The job is not allowed to fail,
so the release pipeline fails.

Check the schedule state first and exit when it is already inactive.
When the schedule is active, the release bot owns it because activation
took ownership, and the PUT succeeds.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

fix(release-platform): skip deactivation when the schedule is inactive

See merge request !1819

## [5.5.2](https://gitlab.com/gitlab-com/gl-infra/common-ci-tasks/-/compare/...) (2026-08-27)

### Fixes

* **release-platform:** skip deactivation when the schedule is inactive ([6a004bfb](6a004bfb))

### Dependencies

* **deps:** update dependency gitlab-org/labkit to v2.37.0 ([36cfb428](36cfb428))