Skip to content

merge queue: embarking main (8d999e6) and #842 together#928

Closed
mergify[bot] wants to merge 12 commits intomainfrom
mergify/merge-queue/b9bad74344
Closed

merge queue: embarking main (8d999e6) and #842 together#928
mergify[bot] wants to merge 12 commits intomainfrom
mergify/merge-queue/b9bad74344

Conversation

@mergify
Copy link

@mergify mergify bot commented Mar 16, 2026

🎉 This pull request has been checked successfully and will be merged soon. 🎉

Branch main (8d999e6) and #842 are embarked together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #842.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue default for merge:

Required conditions to stay in the queue:

---
checking_base_sha: 8d999e69b425dada9ec7922b76bed41531b73aff
previous_failed_batches: []
pull_requests:
  - number: 842
...

maskarb and others added 12 commits March 10, 2026 14:59
Replace QEMU-emulated cross-compilation with native per-architecture
builders (ubuntu-latest for amd64, ubuntu-24.04-arm for arm64) and a
manifest merge step. This eliminates SIGILL crashes caused by QEMU's
incomplete instruction emulation and builds both arches in parallel
for faster CI.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Instead of starting jobs for all components and skipping steps inside,
detect-changes now outputs a JSON matrix of only the components that
need building. Unchanged components don't appear as jobs at all,
making the Actions UI much clearer about what actually built.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
- Add missing permissions block to merge-manifests in prod-release-deploy
- Add fail-fast: false to merge-manifests strategy in both workflows
- Document arch-suffixed tag accumulation as known trade-off

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
- Add sync comment on arch suffixes that must match merge-manifests
- Remove cache-to on PR builds to avoid evicting main-branch cache
- Revert cosmetic backend banner change (CI trigger workaround)
- Fix inconsistent 3-space job indent in prod-release-deploy.yaml

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Add comment in merge-manifests step pointing back to the build job's
arch matrix where the -amd64/-arm64 suffixes are defined.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The public-api component still exists in the repo and should continue
to be built. It was removed from the deploy steps intentionally but
should not have been removed from the build/merge-manifests matrix.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
- Fix dispatch input description: claude-runner → ambient-runner to
  match the matrix entry name, preventing silent no-ops on dispatch
- Add public-api to deploy-to-openshift: output detection, image tag
  determination, and kustomize set image (was built but never deployed)
- Make deploy-with-dispatch conditional: only update operator env vars
  and agent registry ConfigMap for components that were actually built,
  preventing references to non-existent SHA tags
- Make prod release deploy component-aware: iterate built components
  instead of unconditionally setting all image tags, preventing partial
  releases from referencing non-existent release tags

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…ection

Unbuilt components were left pointing at the repo's `:latest` placeholder
because kustomize only updated built components. Now queries the cluster for
currently deployed image tags and seeds kustomize with them before overriding
built components with the release tag.

Also aborts the release job early if the filtered component list is empty to
prevent tagging/releases with no artifacts.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Wrap BUILT list with commas and match against ,COMP, to prevent
substring false positives (e.g. a future "runner" component matching
"ambient-runner").

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@mergify mergify bot closed this Mar 16, 2026
@mergify mergify bot deleted the mergify/merge-queue/b9bad74344 branch March 16, 2026 15:12
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.

1 participant