See https://docs.gitlab.com/user/project/merge_requests/changes/#collapse-generated-files

chore(deps): update pre-commit hook gitlab-com/gl-infra/common-ci-tasks to v3.23

See merge request !1447

chore(deps): update dependency gitlab-com/gl-infra/platform/runway/runwayctl to v4.32.0

See merge request !1452

chore: collapse generated files

See merge request !1451

The OCI Helm chart push (runwayctl helm-chart job) strips the leading
"v" from the tag, so the chart is published as bare semver (e.g.
'1.2.3' for git tag 'v1.2.3') -- matching the same convention as the
generic packages registry.

The publish stage's sync-registry-artifacts skopeo copy was using
${CI_COMMIT_TAG} ('v1.2.3') for the chart URL, so it tried to read
.../chart/<name>:v1.2.3 and got "manifest unknown" -- the chart
exists at .../chart/<name>:1.2.3.

Compute CHART_VERSION="${CI_COMMIT_TAG#v}" and use that in both the
source and destination chart URLs. Mirrors what we already do for the
package version in sync-packages.

Surfaced on the release-platform-canary v1.5.4 publish pipeline:
https://gitlab.com/gitlab-org/security/release-platform-canary/-/jobs/14178495044



Container image sync continues to use ${CI_COMMIT_TAG} as-is because
that's what goreleaser pushes to the container registry (with the v).

Related to delivery#22003

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

fix: strip v prefix from helm chart tag in publish stage smart sync

See merge request !1453

## [3.23.3](https://gitlab.com/gitlab-com/gl-infra/common-ci-tasks/-/compare/...) (2026-05-01)

### Fixes

* strip v prefix from helm chart tag in publish stage smart sync ([1817a66d](1817a66d)), closes [delivery#22003](https://gitlab.com/gitlab-com/gl-infra/delivery/-/issues/)

### Others

* collapse generated files ([e89e5828](e89e5828))

### Dependencies

* **deps:** update dependency gitlab-com/gl-infra/platform/runway/runwayctl to v4.32.0 ([a13bfa33](a13bfa33))
* **deps:** update pre-commit hook gitlab-com/gl-infra/common-ci-tasks to v3.23 ([1c6009bf](1c6009bf))