ci: separate stable image publishing and stabilize ingestion checks - #189
Merged
Merged
Conversation
n30nex
force-pushed
the
codex/beacon-140-release
branch
from
September 30, 2026 20:57
9054acd to
61b0322
Compare
n30nex
changed the title
n30nex
force-pushed
the
codex/beacon-140-release
branch
from
September 30, 2026 22:39
61b0322 to
92a8703
Compare
Drop the deployment-specific rollout notes from the README.
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.
Both application repositories use
devas their default branch, so the existing rule lets development pushes overwritelatest. Remove that branch rule: stable semantic-version tags publishlatest, development builds publishdevand revision tags, and main/prerelease builds leavelatestunchanged.The README records the Beacon/web 1.4.0 rollout: replace CoreScope at
live.meshcore.caafter Alderson's approval and keepdev.meshcore.caas a separate development environment. The server retains its independent version history and is paired with the web release by reviewed revision/digest.The shared ingestion-test subscriber helper now drains readiness probes through a unique marker before packet assertions run. Previously a queued probe could be mistaken for the expected packet event, intermittently failing the advert and scoped-channel tests. This is a test-only correction; production ingestion behavior is unchanged by it.
Current head 61b0322 is refreshed on accepted dev 14354b0, including the partial-telemetry cleanup and corrected counter buckets. Current-base checks, published-head CI, native Go/PostgreSQL tests, restored-copy migration 045 and the 3,200-input replay pass. Both affected tests passed 100 repetitions. The prior eight official metadata-action tag cases still apply to unchanged workflow content.
The Pi review preview runs this head with web 157525ef. The restored migration removed 485 partial telemetry rows while preserving raw counts, valid telemetry and node fingerprints; all 489 matching live rows were separately saved before migration. Private on/off-Pi backups and rollback to the previous pair are retained. Configuration and the other 23 containers were preserved.
No upstream merge, stable tag or production switch was performed. Atlas remains excluded. Release/cutover plan.