Skip to content

[r3.3] ci: improve release workflow robustness and inline debian pkg build#20150

Merged
yperbasis merged 2 commits into
release/3.3from
feature/lystopad/release-workflow-r33-backport
Mar 25, 2026
Merged

[r3.3] ci: improve release workflow robustness and inline debian pkg build#20150
yperbasis merged 2 commits into
release/3.3from
feature/lystopad/release-workflow-r33-backport

Conversation

@lystopad

Copy link
Copy Markdown
Member

Summary

Backport of #19853 (originally cherry-picked to release/3.4 as 38aca05899) to release/3.3.

  • Improve release workflow robustness (early release existence check, artifact verification, non-fatal skopeo delete, GitHub App token for publish step)
  • Inline debian package build — removes the separate reusable-release-build-debian-pkg.yml workflow file
  • Fix debian control file heredoc inside for loop
  • Update docker actions to v4.0.0 (Node.js 24)
  • Pin actions/create-github-app-token to v2.2.1 SHA (Node.js 24)
  • Add disable_version_check input flag
  • Bump actions/checkout, upload-artifact, download-artifact to latest versions
  • Change checkout_ref default to 'release/x.x'operator must set this manually (acts as a safety check to prevent accidentally building from wrong branch)

3.3-specific adjustments (second commit)

  1. mcp excluded from BINARIEScmd/mcp does not exist in release/3.3; it was intentionally kept out of this branch
  2. Re-applied changes skipped by git auto-merge — several hunks were silently resolved to the 3.3 version due to context differences; manually re-applied: checkout_ref default, disable_version_check input, version validation step, and all action version bumps

Test plan

  • Trigger the release workflow on release/3.3 with perform_release=false and verify the build-release + build-debian-pkg jobs complete successfully
  • Verify checkout_ref default shows 'release/x.x' in the workflow dispatch UI (not 'main')
  • Verify reusable-release-build-debian-pkg.yml is gone and debian build runs inline

…build

Cherry-pick of 38aca05 ([r3.4]) to release/3.3.

- Improve release workflow robustness (early release existence check,
  artifact verification, non-fatal skopeo delete, GitHub App token for
  publish step)
- Inline debian package build (removing separate reusable workflow file)
- Fix debian control file heredoc inside for loop
- Update docker actions to v4.0.0 (Node.js 24)
- Pin actions/create-github-app-token to v2.2.1 SHA (Node.js 24)
- Add disable_version_check input flag
- Change checkout_ref default to 'release/x.x' (operator must set explicitly)

Conflict resolution: publish-docker-image job had explicit artifact
download steps in 3.3 that were already removed in 3.4 — dropped them
to match the 3.4 inlined behavior.
…low backport

Manual touch 1 — remove mcp from BINARIES:
cmd/mcp does not exist in release/3.3 (intentionally excluded). The
cherry-pick of 38aca05 did not add mcp (it was a separate prior commit
on 3.4), so BINARIES is already correct. This commit documents the
intentional exclusion.

Manual touch 2 — reapply changes skipped by git auto-merge:
The cherry-pick auto-resolved several sections by keeping 3.3's version
due to context differences. Re-applied the following missing changes:
- checkout_ref default: 'main' -> 'release/x.x' with [MANUAL EDIT REQUIRED]
  description (safety check: operator must set branch explicitly)
- Add disable_version_check workflow input
- Add 'Validate release version against db/version/app.go' step
- Bump actions/checkout to @v6 (all occurrences)
- Bump actions/upload-artifact to @v6 (build-release + test-release)
- Bump actions/download-artifact to @v7 (test-release + publish-release)
@lystopad lystopad requested a review from yperbasis March 25, 2026 13:47
@lystopad lystopad self-assigned this Mar 25, 2026
@yperbasis yperbasis merged commit f60dc87 into release/3.3 Mar 25, 2026
11 checks passed
@yperbasis yperbasis deleted the feature/lystopad/release-workflow-r33-backport branch March 25, 2026 13:59
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