Repository navigation
chore: version packages (beta) - #29
Open
github-actions[bot] wants to merge 1 commit into
Open
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
May 23, 2025 01:53
5c65449 to
c8d4647
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
14 times, most recently
from
August 1, 2025 23:15
02ba53d to
2a6e13e
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
October 22, 2026 14:05
2a6e13e to
002a82e
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
October 22, 2026 14:07
002a82e to
febad86
Compare
This branch has not been deployed
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
mainis currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonmain.Releases
@gud/cli@1.0.0-beta.8
Patch Changes
setData()to the command state to set the data without continuing to the next command, and an optional result type parameter tofork(). FixedbeforeCommandhooks'setData()not reaching the command handler, andafterCommandhooks receiving the command's input instead of its output;afterCommandhooks'setData()now also overrides the data when the command callsnext()orend(). Documented that passingundefinedtonext()orend()keeps the current data andnullclears it.isMiddleware: falsebeing resolved as subcommands, e.g.,hello --name Bobfailing withCommand "Bob" not found. Leading options are now removed using the command's options config regardless ofisMiddleware.binentry in the CLI's package.json, so it's correct when package managers install a shim instead of a symlink (pnpm, and npm or yarn on Windows), and falls back to the script's file name. It can also be set with the newnameoption onrun()andContext, and the lookup is exported asgetBinName. Also madegetHelp,plugin, andPluginErrorruntime exports; they were previously exported as types only.run()is given a command array (including the defaultprocess.argv), e.g.,--name "Bob Smith"failing withCommand "Smith" not found.joinTokens()now quotes tokens with spaces whenever there's more than one token, not only when it's given more than one argument.deploy --target run runresolvingruntwice.removeLeadingOptions()now stops at the first argument that isn't an option or an option's value instead of searching for the next command.--msg 'say "hi"'becomingsay) by passing arguments through resolution and parsing as an array instead of a command string.Contexthas a newargvproperty and acceptsargvinstead ofcommandString, resolved commands haveremainingArgv, thebeforeResolve,beforeResolveNext, andbeforeParsehooks receiveargv, andresolveCommand(),context.resolveCommand(),context.parseCommand(), andremoveLeadingOptions()accept arrays.ParseCommandFnnow receivesstring | string[], and the CLI passes it arrays, so custom parse functions need to handle arrays; support for command strings will be removed in the next major version.splitTokens()now ignores repeated delimiters.