Repository navigation
docs(e2e): fix README blockquote rendering and unpin scenario 18 label - #19
Merged
Merged
Conversation
The E2E_BIN_DIR warning had no blank line after it, so Markdown lazy continuation absorbed the following Scenario 09 paragraph into the blockquote — the whole paragraph rendered inside the warning box. Scenario 18's display label still said upgrade-0.13.5-to-0.15.2 while the suite upgrades to the current checkout, which is now v0.17.0. Co-Authored-By: Claude Opus 5 <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
1 participant
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.
Two small doc defects found during session closeout.
README blockquote — the
E2E_BIN_DIRwarning added in v0.16.0 had no blank line after it. Markdown lazy continuation absorbed the following Scenario 09 paragraph into the blockquote, so the whole paragraph rendered inside the warning box on GitHub.Scenario 18 label — the display string still read
upgrade-0.13.5-to-0.15.2while the scenario upgrades to the current checkout, now v0.17.0. Unpinned toupgrade-0.13.5-to-currentso it stops going stale every release.Docs and one display string only; no behavior change. Verified scenario 18 still passes.
🤖 Generated with Claude Code