chore(release): v5.9.0 pins + changelog (gh-#777) - #803
Merged
Merged
Conversation
…, gh-#723) compose.pinned.yaml moves the five image pins home-v5.8.3 -> home-v5.9.0. CHANGELOG gains the v5.9.0 entry: test tiers, the shared test network, temp-dir cleanup, fake-clock budgets, the stack gate (fresh, capture, upgrade, chaos), nightly.yml, release.yml gating promotion on the gate, the skip-prefix law, and the upgrade note (home-latest and the Release move only after the gate passes). Abstractions unchanged.
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
🏷️ v5.9.0 pins + CHANGELOG (T508 · STORY-450 AC1 · gh-#777)
The pins PR for v5.9.0 — the first release its own gate proves. Merging this moves appliances on
./launch.sh --pinnedto the v5.9.0 images once the tag exists; the tag itself is a separate step.What changes
compose.pinned.yaml: the five image pinshome-v5.8.3→home-v5.9.0(admin_ui, engine, piper, icecast, api).CHANGELOG.md: one v5.9.0 entry covering PR-1…PR-11 (test(fixtures): one shared gw-test docker network for fixture compose (gh-#649) #785–ops(gate): the upgrade leg + role boundary (STORY-446, gh-#777) #790, ops(gate): the chaos legs — api-down and engine-reconnect (STORY-447, gh-#777) #792, ci(nightly): integration tier, chaos legs, one nightly-red issue (STORY-449, gh-#777) #793, ops(gate): T498 bound the api-down silence by total seconds (gh-#777, gh-#791) #798–test(specs): every skip says why, and the obsolete ones are gone (gh-#777, STORY-443) #802): test tiers, the shared test network (Test fixtures exhaust Docker's default address pools under a full-suite run #649), temp-dir cleanup (test: wizard/preflight specs leak temp dirs under /tmp (Story342–346, gh332, pawire) — ~60k dirs / ~500k inodes in a week #710), fake-clock budgets (test-flake: Story243 RendersRideThePerUnitBudget is still a wall-clock race (Orchestration FakeTimeProvider has no timers) — red on the js-yaml dependabot PR #716 #723), the stack gate (fresh, capture, upgrade, chaos), nightly.yml, release.yml gating promotion on the gate, the skip-prefix law, and the upgrade note.git diff v5.8.3..main --stat -- src/GenWave.Abstractions/is empty; the onlysrc/change since v5.8.3 isAdScriptWriter.cs(fake-clock budget, behaviour unchanged on a real clock).Evidence
tools/check-doc-drift.sh→ exit 0 ("pins: all compose.pinned.yaml images pinned to home-v5.9.0").Category!=Integration): 5266 passed / 15 skipped / 0 failed across the nine projects.After merge (T509, Dean)
v5.9.0tag → release.yml runs build-test → build-images → merge-manifests → stack-gate → promote → create-release.home-latestand the Release move only after stack-gate passes; the Release body carries "What this release proved".git pull && ./launch.sh --pinned, then the listening check.Nothing is tagged or merged by this PR.