Repository navigation
feat(release-verify): verify v0.44.0, 34 → 42 passed and 3 → 0 failed, with a deploy freeze, the layout keys and marker counts - #27
Merged
Conversation
…t keys and marker counts - versions.json verifies v0.44.0; the tool versions are unchanged. - 22, 23 and 30 assert the v0.42.2 fixes: the comparison with the branch (record 0111), the row settle writes (0113) and the new escaping (0112). - New scenarios 35 (a deploy freeze, 0115), 36 (compact rows and In sync off keep the destroy lines, 0114) and 37 (counts on a pending row's marker, 0110). - 33 writes a window that crosses midnight UTC as two instead of skipping. - The driver waits for a test bed head ending in ": done", always leaves one, and keeps each run's logs the moment it ends. - findings.md: 42 passed, 0 failed, 3 skipped against v0.44.0. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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.
Verifies Sluiceway
v0.44.0(997546c), three releases after the last verifiedv0.41.0. It checks that the three failures ofv0.41.0are fixed, and adds scenarios for the features ofv0.42.0tov0.44.0.Scenario counts
One local run on the test bed sluiceway/release-verify, 2026-09-25 22:26 to 23:35 UTC, with the owner's
ghlogin as the ticker, in 1,223 requests. The tool versions are the ones the action'se2e.ymlpins at the tag, unchanged: Pulumi v3.263.0, OpenTofu 1.12.6. The counts are cells of the summary, one per scenario and adapter.v0.41.0, its last run (scenarios 1 to 34)v0.44.0(scenarios 1 to 37)Skipped in both: 21, and the
adminpart of 7 for OpenTofu. Both need a second account.The three failures of v0.41.0
Each passes because its fix shipped in
v0.42.2. Each assertion now checks the fix itself:applycompared its commit withmainand refused as moved, with no fresh preview. It started a full scan, which wrote the row pending with the new hash and the failure line. The comment says a newer commit reached the branch.settlewrote the row itself 30 s after the cancel (44 to 63 s onv0.41.0), with statepreview-failed, no box and the failure line. It logsWrote the failure line on the row of ….<span>#</span>1 <span>@</span>sluiceway www.example.com *x*. Neither the dashboard nor the preview page links, mentions or autolinks any part of it.What changed
versions.json:SLUICEWAY_VERSIONisv0.44.0.window: true. The row and the dashboard name the freeze and its reason. "Run workflow" after the end deploys it.pendingDetail: compactandinSyncSection: off, every delete, replace and failure line stays and every marker is unchanged. The in sync rows move whole into the fold of sections that are off, and taking the keys out brings everything back.trackingandbehindare not covered: no fixture moves a resource, and no scenario queues a stack behind another.: donebefore its reset, and always leaves one, even when it fails. It keeps each run's logs the moment the run ends.docs/findings.md: the entry for this verification.docs/release-verification.md: catalogue rows 35 to 37, and 22, 23, 30 and 33 updated.release-verify/README.md: the new file and the new running time (about 70 minutes).No bug of the action was found, so nothing was filed.
🤖 Generated with Claude Code