Repository navigation
docs: record what restoring v0.4.1's docs showed - #44
Merged
Merged
Conversation
PR #43 left two questions for the restore after merge, and re-running Deploy Documentation on v0.4.1's Release run (attempt 2 of 35888419705) answered both on 2026-09-24. An expired github-pages artifact does not block a re-run: the attempt deployed beside the run's day-old expired one, so CONTRIBUTING no longer calls that untested. And a green re-run attempt triggers Verify Release: its first run, 36068815000, started two seconds after the attempt, took the run and attempt from the event, and gave 40 passed, 1 failed, 0 skipped, the failure being TD-2026-09-04's masked publish step read from the carried-over log. The round 2 artifact records both outcomes in place of its after-merge plan, and TD-2026-09-04 cites that first run.
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.
Summary
Records what restoring v0.4.1's Pages docs showed after #43 merged. The
restore re-ran Deploy Documentation on v0.4.1's Release run (attempt 2 of
35888419705) and settled the two questions #43 left open. Docs only.
Type of Change
Changes Made
github-pagesartifact doesnot block a re-run (v0.4.1's re-run deployed beside its day-old expired
one), so the step no longer calls that untested; the conflict needs a
second unexpired artifact, as in v0.2.0's run.
A green re-run attempt triggers Verify Release: its first run,
36068815000,
took the run and attempt from the event and gave 40 passed, 1 failed, 0
skipped, as predicted.
publish step alone.
Testing
Deployment 6649629484 (v0.4.1,
98f14d5) is live, and the site serves therestored build (
.lockreturns 200 again; the exercise's v5 artifact left itout). No code changed.
Checklist
Documentation
Security