Skip to content

chore(ci): use check_previous_channel_release action#154

Merged
duckhawk merged 2 commits into
mainfrom
feat/use-check-previous-channel-release-action
May 14, 2026
Merged

chore(ci): use check_previous_channel_release action#154
duckhawk merged 2 commits into
mainfrom
feat/use-check-previous-channel-release-action

Conversation

@duckhawk
Copy link
Copy Markdown
Member

Summary

  • Replaces the per-repo .github/check_previous_channel_release.sh with the new shared composite action deckhouse/modules-actions/check_previous_channel_release@v14.
  • The shared action fixes the previous-channel version.json parser so it handles both the single-line {"version":"v0.1.14"} layout and the pretty-printed { "version": "v0.1.0" } (multi-line) output produced by yq -o=json.
  • No functional change to the deploy flow; the matrix of editions and the order of steps stay the same.

Test plan

  • Trigger a non-alpha channel deploy (e.g. promote to beta) once deckhouse/modules-actions#73 is merged into v14.
  • Verify the Check previous channel release for <module> step passes when versions match and fails (rejecting the promotion) when they don't.

duckhawk added 2 commits May 13, 2026 11:51
Drops the local .github/check_previous_channel_release.sh in favor of
the deckhouse/modules-actions/check_previous_channel_release@v14
composite action, which fixes the version.json parser so it handles
pretty-printed multi-line output from yq -o=json as well as the
single-line layout.

See deckhouse/modules-actions#73.
The check_previous_channel_release composite action now swaps the
domain of module_source with its `registry` input before pulling, so
the previous-channel image can be read from a read-only registry mirror
without changing the deploy target. Pass `vars.PROD_REGISTRY_READ` to
take advantage of that.

Depends on the swap-domain change in deckhouse/modules-actions (PR #75
for v14).
@duckhawk
Copy link
Copy Markdown
Member Author

Pushed a follow-up commit that switches the registry input for check_previous_channel_release from vars.PROD_REGISTRY to vars.PROD_REGISTRY_READ. The composite action now swaps the domain portion of module_source with that registry input before pulling, so the previous-channel image can be read from the read-only registry mirror without changing the deploy target. Depends on deckhouse/modules-actions#75 being merged into v14 first.

@duckhawk duckhawk merged commit 7ffc35f into main May 14, 2026
11 of 12 checks passed
@duckhawk duckhawk deleted the feat/use-check-previous-channel-release-action branch May 14, 2026 13:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants