fix: revert deploy/initialize workflows to ubuntu-latest (x86 binary dep)#235
Merged
BrianEstrada merged 1 commit intomainfrom Feb 18, 2026
Merged
Conversation
These 3 workflows use slack-notifier-cli-action which downloads an x86-64 only binary. Running on linux-arm64 would break all production deploys. Reverting to ubuntu-latest until slack-notifier-cli ships an ARM64 binary. Other Tier 3 workflows (create-release-tag, publish-tech-docs, allow-deploys, block-deploys, rollback, semgrep, track-pending-release) remain on linux-arm64 as they don't use architecture-specific binaries. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
BrianEstrada
approved these changes
Feb 18, 2026
JesperTerkelsen
added a commit
that referenced
this pull request
Feb 18, 2026
Reverts #235 now that slack-notifier-cli supports ARM64. The slack-notifier-cli-action@main now auto-detects architecture and downloads the correct binary (X64 or ARM64). The ARM64 binary's TLS issue was fixed in slack-notifier-cli v1.3.3 and verified end-to-end. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
JesperTerkelsen
added a commit
that referenced
this pull request
Feb 18, 2026
Reverts #235 now that slack-notifier-cli supports ARM64. The slack-notifier-cli-action@main now auto-detects architecture and downloads the correct binary (X64 or ARM64). The ARM64 binary's TLS issue was fixed in slack-notifier-cli v1.3.3 and verified end-to-end. Co-authored-by: Jesper Terkelsen <jete@monta.com> Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Partial revert of #233 - reverts 3 workflows back to
ubuntu-latestthat useslack-notifier-cli-action.Problem
slack-notifier-cli-actiondownloads an x86-64 only binary (slack-notifier-cli). Running these workflows onlinux-arm64would crash with exec format error, breaking all production deploys.Changes
Revert to
ubuntu-latest:component-deploy.yml- used in every production deploycomponent-deploy-v2.yml- used in newer service deployscomponent-initialize.yml- sends Slack notification at deploy startUnchanged (remain on ARM64)
These 7 workflows from #233 are fine - they don't use architecture-specific binaries:
create-release-tag.yml,publish-tech-docs.yml,allow-deploys.yml,block-deploys.ymlrollback.yml,semgrep-security-scan.yml,track-pending-release.ymlFollow-up
To migrate these 3 workflows to ARM64,
slack-notifier-clineeds an ARM64 binary release (similar to howchangelog-cliships both architectures).