Repository navigation
Upgrade components and bump ESF to 0.6.1 - #35
Merged
Merged
Conversation
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.
ESF now pins Unreal 0.3.1, OpenCode V2 2.0.24 and the opt-in Pi Durable runner 1.0.4, with updated Cube Go SDK, Temporal UI 2.55.0, Python 3.14.8, Go/npm/Python dependency graphs and GitHub Actions. ESF version metadata is synchronized to 0.6.1 across builds, inventories, Python, Helm and image defaults. Embedded frontend and Pi assets were rebuilt, and Unreal's renamed release archive is verified by the installer.
CubeAPI 0.7.2 ignores the SDK's camelCase create-time internet-denial field. The adapter now adds the deployed API's snake_case denial field only for that release; wire-level regressions cover the compatibility boundary. The network probe now asserts direct public HTTPS denial independently of sandbox DNS/proxy failure.
Validation ran inside local Cube microVMs: full Go vet/race/build, 17 Pi regressions, 40 frontend tests/build, intake/brief-lab/eval and release-boundary tests, inventories/SBOM, installer digest rejection, three clean npm audits and a clean secret scan. Conformance, OpenCode, Unreal and Pi factory acceptance produced independently verified patches and confirmed cleanup. Final 0.6.1 metadata, focused race regressions and binary version checks passed. govulncheck found no vulnerable calls; the uncalled stable gRPC advisory is recorded in the upgrade report.
The local Cubelet route-aware configuration was backed up and activated. All three callback/isolation/internet-denial scenarios passed with a temporary, narrowly scoped firewall rule. Automatic approval review rejected persistence pending exact user firewall authorization; this remains a local infrastructure follow-up. The source PR does not change host firewall rules automatically.
See
release/qualification/component-upgrade-2026-10-06.mdfor exact versions, artifacts, run IDs and qualification limits. OpenCode remains the default, Pi remains opt-in, mise's release-age protection remains enabled, and existing production qualification gates remain pending. The dirty primary checkout and unrelated local edits were preserved. This source update does not publish release archives or attest production readiness.Final activated 0.6.1 acceptance after routing:
run-eb463756890b8fb49951f945run-2327e4a977fd9b85b5c224ferun-5524114d8e642753fcdd0dfdPi first failed safely when the gateway stream ended without
finish_reason(run-b0ad997396bb450638007b4b); cleanup passed and a fresh run succeeded. Both receipts are retained. The callback firewall validation rule was removed after testing; persistent callback readiness still requires the pending exact firewall authorization. Cubelet route-aware routing remains enabled.