registry: add trzsz-go (aqua:trzsz/trzsz-go)

[ZeroAurora]

Available in aqua as of v4.493.0.

Verified with export MISE_AQUA_BAKED_REGISTRY=false. Should be merged after baked aqua updated.

[gemini-code-assist]

Code Review

This pull request adds a new tool registration for trzsz-go, providing support for both aqua and github backends. A review comment points out that the github backend requires an explicit executable mapping because the repository name differs from the binary name, which would otherwise prevent the tool from being located correctly.

[gemini-code-assist]

The github backend needs an explicit executable mapping because the repository name (trzsz-go) does not match the primary binary name (trzsz). Without [exe=trzsz], mise will fail to locate the executable within the release assets when falling back to the GitHub backend (e.g., if aqua is unavailable or disabled).

Note that since the tool is registered as trzsz-go, mise will create a shim named trzsz-go. While the aqua backend is capable of exposing all binaries defined in its registry (trzsz, trz, tsz), the github backend fallback will only provide a shim for the tool name itself. If the intention is for users to primarily use the trzsz command, naming the file trzsz.toml would be more idiomatic, though trzsz-go.toml is acceptable to specifically identify this implementation.

Suggested change

	backends = ["aqua:trzsz/trzsz-go", "github:trzsz/trzsz-go"]
	backends = ["aqua:trzsz/trzsz-go", "github:trzsz/trzsz-go[exe=trzsz]"]

[ZeroAurora]

This is false positive. trzsz-go provides three binaries, all of which are made available by mise. This is verified with mise use -g github:trzsz/trzsz-go.

[greptile-apps]

Greptile Summary

This PR adds a registry entry for trzsz-go (aqua:trzsz/trzsz-go) with a github:trzsz/trzsz-go fallback, matching the pattern of the existing trzsz-ssh.toml entry. The format is correct and the PR author verified it with MISE_AQUA_BAKED_REGISTRY=false.

Confidence Score: 5/5

• Safe to merge; the single finding is a minor discoverability suggestion with no impact on correctness.
• The only finding is a P2 style suggestion (missing aliases). All core fields — backends, description, and test — are well-formed and consistent with existing registry entries.
• No files require special attention.

Important Files Changed

Filename	Overview
registry/trzsz-go.toml	New 3-line registry entry for trzsz-go; backends, description, and test fields are well-formed and consistent with the sibling trzsz-ssh.toml entry. Minor: no aliases for the primary trz/tsz binary names.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["mise install trzsz-go"] --> B{Baked aqua registry\nhas trzsz/trzsz-go?}
    B -- Yes --> C["aqua:trzsz/trzsz-go\n(primary backend)"]
    B -- No / MISE_AQUA_BAKED_REGISTRY=false --> D["github:trzsz/trzsz-go\n(fallback backend)"]
    C --> E["Installs trz, tsz, trzsz binaries"]
    D --> E
    E --> F["Test: trzsz --version\nexpected: 'trzsz go {version}'"]

Loading

_{Reviews (1): Last reviewed commit: "registry: add trzsz-go (aqua:trzsz/trzsz..." | Re-trigger Greptile}

[greptile-apps]

Consider adding aliases for primary binary names

The trzsz-go package's main end-user commands are trz and tsz. Without aliases, users who search mise use trz or mise use tsz won't find this package. The registry convention (e.g. ripgrep → rg, github-cli → gh, trzsz-ssh → tssh) is to alias the well-known binary name(s) to the package.

Suggested change

	backends = ["aqua:trzsz/trzsz-go", "github:trzsz/trzsz-go"]
	aliases = ["trz", "tsz"]
	backends = ["aqua:trzsz/trzsz-go", "github:trzsz/trzsz-go"]

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[ZeroAurora]

trzsz has a python version which also uses these two binary names. I don't think this is a good idea.