Skip to content

Fix leading GLOBAL_FLAGS before the command path - #238

Merged
XXPermanentXX merged 4 commits into
mainfrom
fix/leading-global-flags
Oct 14, 2026
Merged

XXPermanentXX merged 4 commits into
mainfrom
fix/leading-global-flags

Conversation

@hopelynd

Copy link
Copy Markdown
Collaborator

Summary

Drop accidental package.json key reordering and tracker.cjs whitespace
edits that were unrelated to the leading GLOBAL_FLAGS fix.
@hopelynd hopelynd closed this Sep 30, 2026
@hopelynd hopelynd reopened this Sep 30, 2026
hopelynd and others added 2 commits October 12, 2026 13:43
- Parse flags once during resolution and reuse them for help and execution
- Validate supplied flags before root/group help and version output
- Preserve bare-command help and skip required flags for help/version
- Only accept explicitly defined flags and localize parser errors by profile language
- Reuse the same positive finite timeout rule for CLI flags and resolved settings
- Cover leading/trailing --config selection without changing active profiles
- Add resolver, timeout, profile, and bilingual credential-domain regression tests
- Update bl/kscli smoke tests and command E2E assertions for localization
- Document flag placement, usage exit codes, and bilingual E2E requirements
@XXPermanentXX
XXPermanentXX merged commit 7d682ed into main Oct 14, 2026
2 checks passed
@XXPermanentXX
XXPermanentXX deleted the fix/leading-global-flags branch October 14, 2026 06:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[bug] --config <profile> silently ignores stored credentials; exits 0 unauthenticated

2 participants