Skip to content

chore(deps): update dependency @optique/core to v1.3.7 - #460

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/optique-core-1.x-lockfile
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/optique-core-1.x-lockfile

Conversation

@renovate

@renovate renovate Bot commented Sep 27, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@optique/core (source) 1.3.0 → 1.3.7 age confidence

Release Notes

dahlia/optique (@​optique/core)

v1.3.7

Compare Source

Released on November 17, 2026.

@​optique/core
  • Fixed fish completion scripts to preserve backslashes in additional
    arguments passed to fish.generateScript(), preventing invalid scripts
    and altered argument values.
    [#​1101, #​1105]
  • Fixed formatMessage() to preserve indentation and other spacing in
    whitespace-only text() terms, including before styled command-line
    examples. CRLF and CR line endings now follow the same formatting rules
    as LF.
    [#​1098, #​1104]
  • Fixed hidden commands disappearing from the usage synopsis in their own
    help and their descendants' help. Commands remain hidden in parent
    synopses according to their visibility setting.
    [#​1110, #​1113]
  • Fixed map() losing bindEnv() and bindConfig() fallbacks inside
    composed commands, and making prompt() skip mapped optional() or
    withDefault() parsers when context annotations were present.
    [#​1108, #​1109]
  • Fixed the completion option form (--completion) leaving its internal ARG
    in usage lines and help entries when hidden. The argument now follows the
    option's hidden setting.
    [#​1097, #​1130]
  • Improved parsing performance for long lists of positional arguments and
    repeated option values, including multiple() state updates, while
    preserving dependency replay and isolation between parser alternatives.
    [#​1122, #​1123, #​1124, #​1128]
@​optique/discover
  • Fixed runProgram() root commands consuming registered command names or
    enabled help, version, and completion command names as positional values.
    Registered command results and errors now take precedence over root parsing,
    and meta commands remain reachable without losing root help or completion.
    createProgramParser() keeps its existing parser precedence.
    [#​1102, #​1106]
  • Fixed runProgram() to show complete root help for an unknown top-level
    command followed by --help when source contexts are registered, instead
    of throwing a TypeError or omitting nested command paths.
    [#​1132, #​1133]

v1.3.6

Compare Source

Released on October 15, 2026.

@​optique/core
  • Fixed Bash completion of joined option values with = for long -
    options or : for / options and default or customized word-break
    settings, including :/@ in values or option names. Completion respects
    the cursor position, stops at unquoted shell operators, and decodes
    quoted or escaped values, including incomplete ANSI-C control escapes,
    without executing shell substitutions. File values preserve their full
    prefix and filtering metadata when option names overlap, unquoted tilde
    expansion after quoted or split option names, and quoted path prefixes.
    Exact literal candidates, including dot-prefixed values, remain available
    alongside file suggestions when hidden files are excluded. Hidden candidates
    allowed by one file suggestion remain available alongside other file
    suggestions. Option names quoted or escaped from their first character,
    partial option names, and literal values resembling file
    completion markers also complete correctly. File suggestions with fixed
    search patterns enumerate matching paths instead of inserting the pattern
    as literal text, retain wildcard filters as values are typed, and honor
    hidden-file settings without duplicate directory candidates, including on
    older Bash versions. Fixed-pattern completion also preserves a typed ./
    prefix or its omission even for empty values, completes explicitly typed
    hidden directories, follows nocaseglob when narrowing candidates, and
    removes duplicate matches from overlapping patterns. Control characters in
    joined fixed patterns no longer split or corrupt completion records.
    Wildcard directory components remain navigable, and completion filters even
    partial or unrelated typed prefixes instead of replacing them with all
    matches. Large candidate sets remain responsive without changing suggestion
    order. Typed tilde or absolute path forms remain intact when fixed patterns
    use a different spelling. Bare unquoted ~ values also complete
    home-relative patterns. Fixed Bash patterns treat brackets, backslashes,
    and extended-glob operators literally alongside */? wildcards.
    Navigating into suggested directories retains fixed basename filters for
    subsequent completions, including directory-only patterns and patterns
    rooted directly at /. Unquoted fixed wildcard patterns still expand when
    entered in full, while quoted or escaped wildcard prefixes remain literal.
    A lone . prefix also completes ./ patterns, and navigation through ..
    no longer offers descendants outside matching pattern bases while allowing
    parent-relative patterns and navigation that stays within their bases.
    Completion candidates remain available when sort is missing.
    [#​1031, #​1032, #​1033, #​1079]

  • Fixed Bash file completion to quote filenames containing spaces or shell
    metacharacters, preserving them as literal arguments when the completed
    command runs. Directory paths remain open for further completion.

    Bash 3.2 lacks compopt, so filename processing applies to all suggestions
    there. On that version, a literal suggestion matching
    a local directory receives a trailing slash instead of a space.
    [#​1030, #​1034]

  • Fixed Nushell completion scripts generated by nu.generateScript() to
    pass fixed callback arguments containing apostrophes to the CLI intact.
    Previously, an argument such as it's arrived as its.
    [#​1039, #​1057]

  • Fixed Nushell completion to pass the command line to the CLI with the
    same arguments Nushell itself would pass. Empty quoted arguments such as
    "" are no longer dropped, so options after them complete again.
    Escaped quotes in double-quoted strings, backtick strings, and raw strings
    such as r#'...'# are now decoded instead of being split or merged with
    later arguments, and a space typed inside an unfinished quoted value no
    longer starts a new argument.
    [#​1041, #​1065]

  • Fixed Nushell completion to quote suggested values and file names that
    contain spaces, quotes, or other characters Nushell would interpret, so
    each completed value stays a single argument with its original text.
    The completion menu still shows the values unquoted.
    [#​1038, #​1076]

    Because quotes keep Nushell from expanding ~, a quoted path typed
    under the home directory is inserted with the home directory spelled out.

  • Fixed Nushell file completion leaving out symbolic links to files and
    directories. A link is now classified by its target, so a directory link
    gets a trailing slash for navigation, while extension filters still match
    the link's own name. Broken links stay excluded when completion is
    limited to files or directories.
    [#​1042, #​1063]

  • Fixed Nushell file completion to treat square brackets in a typed path as
    literal characters. Completing report[1] now suggests report[1].txt
    instead of matching report1.txt as if [1] were a glob character class.
    [#​1040, #​1060]

  • Fixed Nushell, zsh, and PowerShell file completion to retain fixed glob
    filters while narrowing a path prefix. Directories remain available for
    navigation.
    [#​1049, #​1077]

  • Fixed PowerShell and Nushell file completion to match compound extensions
    such as .tar.gz, while keeping directories available for navigation.
    [#​1048, #​1061]

  • Fixed PowerShell completion for quoted literal values and file paths,
    including unfinished quotes and joined option values, so suggestions
    remain literal arguments when inserted.
    [#​1045, #​1070]

  • Fixed PowerShell completion to ignore arguments after the cursor when
    completing an earlier argument, keeping later arguments intact.
    [#​1043, #​1069]

  • Fixed PowerShell completion to quote literal values and file/directory
    paths when needed, preserving their argument values when the completed
    command runs. Completion labels remain readable, and completing a quoted
    directory keeps the cursor ready for its child paths.
    [#​1046, #​1068]

  • Fixed PowerShell file completion to respect case in extension filters,
    matching the path parser's case sensitivity.
    [#​1044, #​1067]

  • Fixed Zsh completion for regular-file suggestions, including
    path({ type: "file" }), to exclude named pipes and other non-regular paths
    even without an extension filter. Symlinks to regular files and directory
    navigation remain available.
    [#​1053, #​1073]

    File suggestions now consistently use the files/directories completion
    tags. The file-patterns style and globbed-files/all-files tag styles
    no longer control suggestions without an extension filter. The
    list-dirs-first style still lists directories before regular files.

  • Fixed Zsh completion to match option values inside single/double quotes,
    including values with literal backslashes and file paths with spaces,
    while preserving their quoting context and backend file-pattern globs.
    [#​1056, #​1078]

  • Fixed Zsh completion to offer initial matches for relative file globs such
    as tmp/fixtures/*.txt when the current value is empty. This also
    applies to suggestions with type: "any", which can match FIFOs. File
    extension filters still apply to these matches, and subdirectories remain
    available for navigation. Initial matches honor the tag-order,
    list-dirs-first, and recursive-files styles. Directory-only
    suggestions now also offer initial matches, limited to directories whose
    names match the glob. Initial glob matching supports only * and ?
    wildcards in the filename; filename patterns containing brackets or
    backslashes retain their previous completion behavior.
    [#​1054, #​1075]

  • Fixed Zsh completion to preserve literal values containing colons or
    backslashes, including URL choices. Regenerate and reload existing Zsh
    completion scripts to apply the fix.
    [#​1055, #​1058]

  • Fixed Zsh literal completion with COMPLETE_IN_WORD enabled to complete
    values in the middle of a word, matching the text before and after the
    cursor.
    [#​1052, #​1072]

  • Fixed fish completion to decode quotes and backslash escapes in the word
    being completed, so --format "tw or --file two\ w now offers the same
    choices and file names as the unquoted word. A quoted or escaped ~ now
    stays a literal path, as in fish's own file completion.
    [#​1035, #​1064]

  • Fixed fish completion to offer files matching a file suggestion's wildcard
    pattern, such as *.txt, file?.txt, or src/*.txt. These patterns
    previously produced no candidates. Hidden entries are now included for
    such patterns when includeHidden is enabled, and a pattern under /
    now lists the root directory.
    [#​1037, #​1062]

  • Fixed fish file completion to suggest filenames that start with a dash,
    such as -n, -e, or -s, which were previously missing from the
    candidates. Completing dash-prefixed paths no longer prints basename
    errors to the terminal either.
    [#​1036, #​1059]

  • Fixed shell completion values starting with __FILE__: being interpreted
    as file completion requests instead of literal suggestions.
    [#​1051, #​1066]

    Regenerate saved completion scripts after upgrading. Custom completion
    producers/adapters must encode/decode the __LITERAL__: escape for values
    starting with __FILE__: or __LITERAL__:.

  • Fixed zsh/fish completion scripts for program names containing hyphens or
    dots to keep their commands separate when installed together with scripts
    for similarly named programs, such as foo-bar, foo_bar, and foo.bar.
    Regenerate completion scripts for all affected programs after upgrading.
    [#​1047, #​1071]

  • Fixed file value completion in keyValue() to match the value path while
    retaining the key and separator in inserted candidates.
    [#​1050, #​1074]

    Regenerate installed shell completion scripts after upgrading. In Bash,
    a custom separator containing word-break characters other than =, such
    as :, still needs to be removed from COMP_WORDBREAKS so completion
    receives the key/value as one word.

v1.3.5

Compare Source

Released on October 12, 2026.

@​optique/core
  • Fixed option and flag completion to stop suggesting option names and values
    after the -- option terminator.
    [#​1028, #​1029]

v1.3.4

Compare Source

Released on October 10, 2026.

@​optique/core
  • Fixed subcommand help to retain the selected command's brief, description,
    and footer when commands are wrapped in object(), tuple(), or
    concat(), including labeled objects and nested command groups. This also
    preserves custom page metadata through merge(), decorators that copy or
    edit documentation, and duplicate package instances, including mixed
    ESM/CommonJS builds. Command page descriptions no longer pick up text
    from sibling custom parsers or edited options.
    [#​1021, #​1022]

v1.3.3

Compare Source

Released on October 6, 2026.

@​optique/core
  • Fixed formatMessage() and formatDocPage() starting automatically
    wrapped lines with a space. When a text term that begins with a space,
    a values() separator, or a showDefault/showChoices prefix such as
    the default " [" wraps onto a new line, its leading whitespace is now
    dropped, so the line starts at the same column as the text above it.
    Leading whitespace at the start of a message, after lineBreak(), or in
    value() and values() items is kept. [#​1003, #​1006]
@​optique/run
  • Fixed run(), runSync(), and runAsync() truncating help, version,
    completion, and error output when it was piped into a slow reader on
    Node.js or Bun. The process used to exit with the expected code after
    only the first few kilobytes had been delivered. When standard output
    or standard error is a pipe or a file on POSIX systems, the default
    writers now write directly to its file descriptor and return only after
    the whole text has been written, so the exit that follows no longer
    discards the rest. printError() with exitCode does the same before
    it exits, which means a mock of process.stderr.write() no longer sees
    its message in that case. Terminals, Windows, and Deno are unaffected,
    and custom stdout, stderr, and onExit callbacks work as before.
    [#​1008, #​1010]
@​optique/man
  • Fixed formatUsageTermAsRoff(), formatDocPageAsMan(), and the
    generateManPage*() functions to render required options without optional
    brackets in the man page SYNOPSIS, including options in exclusive branches
    and required repetitions. Required option aliases now use
    parentheses, such as (-n | --name) STRING, to preserve their grouping.
    [#​1004, #​1012]

v1.3.2

Compare Source

Released on September 29, 2026.

@​optique/core
  • Reduced typo suggestion overhead when option parsers encounter positional
    arguments. Literal errors.noMatch messages now skip suggestion searches,
    and candidates whose length difference exceeds the suggestion thresholds
    are excluded before calculating edit distances. Suggestion results and
    custom error callback invocations are preserved.
    [#​988, #​992]
  • Fixed passThrough() hiding errors for known options in object(),
    tuple(), and concat(), including missing values and Boolean options
    given attached values. Unknown options are still forwarded, and ordinary
    alternative parsers can still recover from consuming failures.
    [#​991, #​993]
  • Fixed argument() accepting joined option tokens such as --name=value
    as positional arguments before --. Unknown joined options now reach
    passThrough(), and errors from known options are no longer hidden by
    positional arguments. Use -- to pass joined option tokens as literal
    positional arguments.
    [#​990, #​995]

v1.3.1

Compare Source

Released on September 26, 2026.

@​optique/core
  • Fixed a Boolean option() given an attached value, such as
    --no-pager=1, reporting the option name with the = or : separator
    still attached in its error message.
    [#​966, #​975]

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@socket-security

socket-security Bot commented Sep 27, 2026 •

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatedvitepress@​2.0.0-alpha.20 ⏵ 2.0.0-alpha.2198 +110091 +594 +490
Added@​optique/​core@​1.3.7991009296100

View full report

@renovate
renovate Bot force-pushed the renovate/optique-core-1.x-lockfile branch from 7e5da2f to 42a1133 Compare September 30, 2026 20:38
@renovate renovate Bot changed the title chore(deps): update dependency @optique/core to v1.3.1 chore(deps): update dependency @optique/core to v1.3.2 Sep 30, 2026
@renovate
renovate Bot force-pushed the renovate/optique-core-1.x-lockfile branch 2 times, most recently from 8c86512 to 80822a2 Compare October 7, 2026 11:14
@renovate renovate Bot changed the title chore(deps): update dependency @optique/core to v1.3.2 chore(deps): update dependency @optique/core to v1.3.3 Oct 7, 2026
@renovate
renovate Bot force-pushed the renovate/optique-core-1.x-lockfile branch from 80822a2 to 646eb5d Compare October 10, 2026 18:13
@renovate renovate Bot changed the title chore(deps): update dependency @optique/core to v1.3.3 chore(deps): update dependency @optique/core to v1.3.4 Oct 10, 2026
@renovate
renovate Bot force-pushed the renovate/optique-core-1.x-lockfile branch from 646eb5d to 1f258da Compare October 13, 2026 12:50
@renovate renovate Bot changed the title chore(deps): update dependency @optique/core to v1.3.4 chore(deps): update dependency @optique/core to v1.3.5 Oct 13, 2026
@renovate
renovate Bot force-pushed the renovate/optique-core-1.x-lockfile branch from 1f258da to 56307da Compare October 15, 2026 23:16
@renovate renovate Bot changed the title chore(deps): update dependency @optique/core to v1.3.5 chore(deps): update dependency @optique/core to v1.3.6 Oct 15, 2026
@renovate
renovate Bot force-pushed the renovate/optique-core-1.x-lockfile branch 2 times, most recently from b2e6df0 to 0226b84 Compare November 2, 2026 18:32
@renovate
renovate Bot force-pushed the renovate/optique-core-1.x-lockfile branch 2 times, most recently from ea00b7e to 618df32 Compare November 11, 2026 19:13
@renovate
renovate Bot force-pushed the renovate/optique-core-1.x-lockfile branch from 618df32 to daf858e Compare November 16, 2026 21:32
@renovate
renovate Bot force-pushed the renovate/optique-core-1.x-lockfile branch from daf858e to 9113788 Compare November 18, 2026 03:02
@renovate renovate Bot changed the title chore(deps): update dependency @optique/core to v1.3.6 chore(deps): update dependency @optique/core to v1.3.7 Nov 18, 2026
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.

0 participants