Repository navigation
release(rc): dual ESP32-P4 firmware + simulator GPS-GM PTP / SV candidate - #359
Merged
masarray merged 5 commits intoNov 4, 2026
Merged
Conversation
… promotion intent
…or prerelease without rebuilding
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
masarray
added a commit
that referenced
this pull request
Nov 4, 2026
…setup ZIP (#360) Promote operator-accepted RC1 binaries without changing GUI/firmware runtime. Pin exact PR #359 source SHA and firmware checksums; package correct Inno Stable AppId and verified Windows Setup ZIP; preserve portable Windows ZIP, Linux AppImage and distinct pre-v3/v3.x firmware. Update public landing downloads to prefer installer ZIP with fallback and avoid unsafe single-BIN v3.x links. Maintain explicit v3.x hardware engineering-preview qualification and historical M3.H.3/RC1 release integrity. PR #360 exact head f624cc6 — 7/7 CI PASS and no outstanding review thread. The one-time stable publication workflow runs on the added release-launch document, with a separate installer smoke and SHA256 gate.
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
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.
Purpose — Public dual-revision Process Bus Simulator RC1
Canonical product contract is now in main AGENTS.md, commit 5925e17: ARStack61850 must emulate SCL-configured IEC 61850 virtual Merging Units and a fully featured GPS-style PTP Grandmaster over real Ethernet packets in an isolated lab. A physical GPS antenna is NOT a simulator acceptance gate. Preserve 4I+4V, 4000 fps/MU, canonical BER and full M4 3-MU SCL workflow.
Production runtime fix
AUTO smpSynch=2for the explicitly enabled simulated-global SOURCE only when existing live simulated GM PTP/TX evidence and the canonical SV sample/MAC phase qualification are BOTH valid.Publication pipeline
docs/releases/PROCESSBUS_DUAL_RC_LAUNCH.mdinitiates once-only RC publication after merge..github/workflows/processbus-dual-rc-publish.ymlis promotion-only: finds the merged PR exact-head, verifies all its GitHub checks GREEN and the existing ARStack Studio Native Preview run successful, downloads the already-built Windows installer/portable, Linux AppImage and ESP32-P4 revision-aware dual firmware artifacts; verifies manifest/catalog/SHA, two distinct compiled revision images and Windows embedded firmware; then creates public prerelease tagprocessbus-sim-dual-rc1-20261105.Required gate
Do NOT merge until exact-head C++/Windows/Linux/ESP32-P4/Native Preview checks GREEN, zero unresolved review objections, exact firmware build identity. Merge using squash title that starts with
release(rc):so the publisher can resolve its source and publish. Do not trigger old v0.1.1 single-firmware release workflow.