Repository navigation
Release v1.6.1: correct version flags, alias ordering, and reader guides - #43
Merged
Merged
Conversation
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.
Version requests previously failed after named commands, and repeated mixed
aliases could retrieve an earlier long-option value instead of the last input.
This release reserves
-v/--versioncase-insensitively at every scope andshares ordered lookup between validation and command execution.
tool greet --name Alice -n Bobnow uses Bob.tool repo clone -vdisplays theapplication version and skips dispatch;
--name=--versionremains a value.Conflicting runtime definitions and generator specs now fail clearly. Verbose
examples use
-d/--verbose; the generator's owninit --version <value>configuration option remains distinct.
The current guides correct binary paths, snippet insertion, Boolean/default
lookup, colour/NO_COLOR semantics and locale/casing explanations. A new required
CI check compiles current Markdown and executes its platform-specific recipes.
Local qualification: 78 framework tests; complete Windows generator suite;
PowerShell completion contract; 18 Markdown programs and 68 compiler/process
invocations; normal and clean-clone Lazarus package builds; eight-example cleanup
smoke; DocKit 1.0.0 check/build; all 14
rendered pages inspected in isolated Edge with no logged browser errors.
The final enum recipe sits below its option table because the pinned DocKit
renderer splits pipes inside table code. Its complete registration is compiled
with the other documented options; rendered table column counts are checked.
The exact final PR revision must pass Linux and Windows CI. The merge commit
will be qualified again before creating the annotated v1.6.1 tag and publishing.