chore(release): realign develop with main after the #673 and #677 promotions - #678
Merged
Conversation
chore(release): promote develop to main — repair the agent-runtime image build main could not build the agent-runtime image: the OPA download used BusyBox wget, which exits 0 without writing the file when the URL redirects to another host. Replaced with curl -fsSL plus test -s, verified by building the image — opa reports Version 1.19.0 from an ELF binary.
chore(release): promote develop to main — the agent-runtime image build, actually fixed .gitignore ignores .harness/bin/, so git tracks no file there and a clean checkout has no such directory: mv failed for want of a destination, never a download. mkdir -p before the move. Verified in a clean git worktree on linux/amd64 --no-cache, which is what the runner actually checks out.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
📊 Bilingual Coverage ImpactPR Changes
Repository Coverage
✅ Good: All EN changes have ES counterparts. Generated by GitHub Actions |
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
1 participant
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.
Pull Request Summary
Sync-back after two promotions. Zero file changes —
git diff develop..mainis empty; both commits are the merge nodes GitHub created onmainwhen #673 and #677 landed.Two rather than one because #674 — the sync-back after #673 — was closed instead of merged: its red
Build & Push Services (GHCR)was true about main, which genuinely could not build the agent-runtime image at the time. Promoting the real fix repaired main directly and made that PR obsolete. This one collects both merge nodes.With this merged, both branches of this repository converge, and the BeyondNetCode organisation is fully in sync:
beyondnetcode/umsalready hasmainanddevelopon the same commit.Before you submit
db596547.Linked ADRs / Issues
db596547, the same realignment after chore(repo): pin Node at the root, and drop a Sponsor button that leads nowhere #637What the reviewer should know
Nothing here changes a line, so any red belongs to the branch state rather than to this change.
One recurring cost worth naming: this is the fourth realignment PR, because every promotion leaves
developa merge node behind. Thepre-pushrelease macro was written to run both phases in one go, but branch protection ondevelopandmainblocks the push path it takes — so these follow-ups stay manual until either the macro learns to open PRs, or promotions switch to a strategy that does not leave a node behind.🤖 Generated with Claude Code