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

See merge request !1440

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

See merge request !1442

- The tube component allows subscriber projects to build GitLab
  related projects in a controlled and uniform environment, ensuring
  compatibility of dependencies.
- For more details see:
  gitlab-org/distribution#51

.

Signed-off-by: Alec Xu <axu@gitlab.com>

feat: tube component addition

Closes gitlab-org/build/architecture/tube/tube#2

See merge request !1413

Initial support introduced in
!1413

feat: add initial T.U.B.E. integration

See merge request !1446

## [3.23.0](https://gitlab.com/gitlab-com/gl-infra/common-ci-tasks/-/compare/...) (2026-04-29)

### Features

* add initial T.U.B.E. integration ([21ed9b44](21ed9b44))

### Dependencies

* **deps:** update dependency gitlab-com/gl-infra/platform/runway/runwayctl to v4.29.0 ([0fc77891](0fc77891))
* **deps:** update pre-commit hook gitlab-com/gl-infra/common-ci-tasks to v3.22 ([e9c63302](e9c63302))

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

See merge request !1445

The sync-packages job script lives inside an unquoted heredoc in the
generate-publish-pipeline generator. A comment line containing literal
backticks ("Using \`case\` over...") was being parsed as command
substitution by the outer shell at heredoc-write time, where it tried
to execute "case" as a command and failed with:

  /bin/sh: eval: line 263: syntax error: unexpected end of file (expecting word)

This bug had been latent since v3.22 (when the case statement and its
comment were added), but only surfaced once a project actually exercised
the publish stage with release_platform_enabled: true on a tag pipeline
(release-platform-canary v1.4.2).

Fix: rewrite the comment without backticks. Verified the fix with sh -n
in alpine:3.21 against the regenerated release-platform.yml.

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

fix: escape backticks in publish stage heredoc comment

See merge request !1448

## [3.23.1](https://gitlab.com/gitlab-com/gl-infra/common-ci-tasks/-/compare/...) (2026-04-29)

### Fixes

* escape backticks in publish stage heredoc comment ([1a54923b](1a54923b))

### Dependencies

* **deps:** update dependency gitlab-com/gl-infra/platform/runway/runwayctl to v4.31.0 ([25ab6880](25ab6880))

The quay.io/skopeo/stable image's entrypoint is `skopeo`. GitLab CI
runs job scripts via `<entrypoint> sh -c "<script>"`, so the resulting
invocation is effectively `skopeo sh -c ...`, where skopeo parses `sh`
as a subcommand and fails on the unrecognized `-c` flag:

  time="..." level=fatal msg="unknown shorthand flag: 'c' in -c"

Override the entrypoint to an empty list so GitLab CI can run sh
directly:

  image:
    name: quay.io/skopeo/stable:v${SKOPEO_VERSION}
    entrypoint: [""]

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



Related to delivery#22003

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

fix: override skopeo image entrypoint in sync-registry-artifacts

See merge request !1449

## [3.23.2](https://gitlab.com/gitlab-com/gl-infra/common-ci-tasks/-/compare/...) (2026-04-30)

### Fixes

* override skopeo image entrypoint in sync-registry-artifacts ([854bb710](854bb710)), closes [delivery#22003](https://gitlab.com/gitlab-com/gl-infra/delivery/-/issues/)

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))