Ahoy: baixar versions anteriors

A patch release that fixes a v3 regression in tab completion, and makes release downloads verifiable.
If you use a completion script written for Ahoy v2, please upgrade. In v3.0.0 and v3.0.1, pressing Tab after a command name could run that command.
Fixes
Tab completion no longer (accidentally) runs your commands.
#193, reported and fixed by @hanoii in #194.
Completion scripts from the v2 (urfave/cli) era, including the bash script in our own docs, work by adding --generate-bash-completion to the words typed so far:
opts=$( ${COMP_WORDS[@]:0:$COMP_CWORD} --generate-bash-completion )
So ahoy deploy <TAB> runs ahoy deploy --generate-bash-completion. Since v3.0.0, Ahoy's own flags are only recognised before the command name. That meant the flag was passed to deploy as an ordinary argument, and deploy ran.
──────────────────────────────────────┬──────────────────┬───────
Typed │v3.0.1 │v3.0.2
──────────────────────────────────────┼──────────────────┼───────
ahoy foo <TAB> │runs foo │nothing
──────────────────────────────────────┼──────────────────┼───────
ahoy foo dis<TAB> │runs foo dis │nothing
──────────────────────────────────────┼──────────────────┼───────
ahoy bar <TAB> (bar imports baz and │prints help for │baz qux
qux) │bar │
──────────────────────────────────────┼──────────────────┼───────
ahoy bar ba<TAB> │prints help for │baz qux
│bar │
──────────────────────────────────────┴──────────────────┴───────
A --generate-bash-completion that comes last is now treated as a completion request. Ahoy lists the subcommands of the command you typed and runs nothing, as v2 did. Anywhere else in the arguments, it still reaches your command unchanged, so wrapped tools that take a flag of that name still receive it.
Cleaner completion from ahoy completion <shell>
The same PR fixes the completion scripts that ahoy completion bash|zsh|fish|powershell generates, when you complete the first word after ahoy:
- Each command is listed once, instead of twice.
- Hidden commands, such as __complete and anything marked hide: true, are no longer suggested.
- Suggestions now match what you've typed. ahoy f<TAB> gives foo fo instead of the full command list.
- Aliases are still offered alongside command names.
Completion of subcommands and of later arguments is unchanged.
Thanks
- @hanoii (Ariel Barreiro) for reporting #193 with a clear before-and-after table, and for the fix and tests in #194. This is Ariel's second regression fix in two releases.
Full changelog
- #190, #192 Include the raw binaries in the checksums file, and sign it with cosign
- #194 Stop legacy completion from running commands (@hanoii), fixes #193
- Updated the README sponsors section
Full diff: v3.0.1...v3.0.2

Ahoy v3.0.1
A patch release fixing three regressions in v3.0.0, plus one new feature.
If you are on v3.0.0, please upgrade! Two of these bugs changed the arguments your commands received without telling you: the wrapped tool ran, exited 0, and may well have done something other than what you typed. Sorry.
Fixes
Interactive and full-screen commands work again
#180, reported and fixed by @hanoii in #181.
v3.0.0 replaced the process-wide os.Stderr with a pipe (for reason while in the early stages of migrating to Cobra), so every child process inherited a pipe on fd 2 instead of the terminal. Anything that draws a TUI on stderr could no longer ask the terminal how big it was, measured 0x0, and rendered nothing. gum on Bubble Tea v2 crashed outright with makeslice: len out of range.
That covers gum, fzf, glow, progress bars, spinners, and anything else that repaints the terminal (or bits of it) in place.
# v3.0.0
$ ahoy fds
l-wx------ ... /proc/self/fd/2 -> 'pipe:[3079507]'
# v3.0.1
$ ahoy fds
lrwx------ ... /proc/self/fd/2 -> /dev/pts/2
Ahoy no longer displaces anything on stderr. Output is not buffered either, so a long-running command's output appears as it is produced.
A follow-up (#184) removed the pipe entirely. It turned out to be dead code: it had been added to intercept Cobra's error output during the v3 migration, that job had since moved elsewhere, and what remained copied stderr to stderr, achieving nothing except the loss of the terminal.
Command arguments are passed through verbatim
#182, reported by @jurgenhaas, fixed in #185. Also closes #163, raised by @AlexSkrypnyk.
v3.0.0 let Cobra parse each command's arguments before running it. Any flag it did not recognise was silently dropped, along with the token following it.
$ ahoy echoargs AAA --log-junit x.xml --configuration y.dist BBB
AAA BBB # v3.0.0
AAA --log-junit x.xml --configuration y.dist BBB # v3.0.1, and v2.5.0
Because Ahoy is often used to wrap other CLIs, this was quiet rather than loud. Reported effects included phpunit --configuration <path> --list-suites receiving nothing at all, chown -R www-data:www-data . arriving as chown ., and mkdir -p /tmp/logs arriving as mkdir.
Ahoy's own flags were being claimed after the command name too, which was the same defect, driven by a CLI change that I decided was actually counterproductive. Something like ahoy phpunit -v turned on Ahoy's verbose mode instead of PHPUnit's.
All text after the command name now reaches your command exactly as typed, in order. Ahoy's own flags are recognised only before the command name.
ahoy --verbose deploy # --verbose is Ahoy's
ahoy deploy --verbose # --verbose belongs to the deploy command
Two things to know when upgrading:
- ahoy <command> --help now reaches the wrapped tool, so ahoy drush --help gives you Drush's help. Ahoy's own help for a command is ahoy help <command>. That form was documented but didn't work correctly, and is now a real command.
- -v and --verbose after a command name belong to the command. Put them before the command name for Ahoy's verbose output.
This also resolves #163: appending arguments has never needed --, and now does not lose them either.
A literal -- reaches your command
#186, fixed in #187.
Ahoy removed every -- a user typed, not just a leading one, so a separator meant as data never arrived. Lots of tools need to use those.
───────────────────────────────┬──────────────────────────┬─────────────────────────────
Typed │v3.0.0 │v3.0.1
───────────────────────────────┼──────────────────────────┼─────────────────────────────
ahoy k exec mypod -- ls /app │kubectl exec mypod ls /app│kubectl exec mypod -- ls /app
───────────────────────────────┼──────────────────────────┼─────────────────────────────
ahoy npm run build -- --verbose│npm run build --verbose │npm run build -- --verbose
───────────────────────────────┼──────────────────────────┼─────────────────────────────
ahoy cargo run -- --port 8080 │cargo run --port 8080 │cargo run -- --port 8080
─────────

ahoy v3.0.0 - The Almost DrupalSouth Release
Ahoy v3 migrates the CLI framework from urfave/cli v1 to spf13/cobra.
Every existing .ahoy.yml file SHOULD continue to work unchanged - at the moment ahoyapi: v2 is still the current config
file format flag, and there are no breaking changes to the command syntax or behaviour. Updates to the configuration file format are likely to happen in the next 6-12 months though, but ahoy release versions will be forwards-compatible.
Upgrading
For most people this is a drop-in replacement. Two things to be aware of:
1. Homebrew
brew install ahoy now installs v3. There is no ahoy@2 formula - a versioned formula was
submitted to homebrew-core and declined as against their policy. If you need to stay on v2, use
the binaries or archives attached to the
v2.5.0 release.
I will continue to monitor the v2 release line code for security issues, dependency upgrades etc, and will release minor version updates as and when required, for at least the next 6 months.
2. 32-bit ARM builds are now split into armv6 and armv7
Previous releases shipped a single ahoy-bin-linux-arm built for ARMv6. v3 builds ARMv6 and ARMv7 separately, so that asset is replaced by two:
─────────────────────┬─────────────────────────────────────────────────
v2.5.0 │v3.0.0
─────────────────────┼─────────────────────────────────────────────────
ahoy-bin-linux-arm │ahoy-bin-linux-armv6 and ahoy-bin-linux-armv7
─────────────────────┼─────────────────────────────────────────────────
ahoy-linux-arm.tar.gz│ahoy-linux-armv6.tar.gz and
│ahoy-linux-armv7.tar.gz
─────────────────────┴─────────────────────────────────────────────────
If you hand-wrote a download URL ending in -linux-arm, point it at -linux-armv6 (identical to
what you had) or -linux-armv7 (better performance on Raspberry Pi 2 and newer). The install
one-liner in the README selects the right one automatically.
All other asset names are unchanged from v2.5.0. Static Linux builds
(ahoy-bin-linux-amd64-static, ahoy-bin-linux-arm64-static) are new in v3 and useful for minimal containers.
What's new
ahoy config command group
Two new subcommands:
- ahoy config validate: validates .ahoy.yml files, with version mismatch detection and
field-level checks that catch unsupported features
- ahoy config init: the command that downloads a "starter" .ahoy.yml file, is now reworked to use Go's native HTTP client, dropping external dependencies
New environment variables
- AHOY_CMD: absolute path to the running ahoy binary (via os.Executable()). Nested ahoy
calls can use $AHOY_CMD to guarantee they invoke the same binary version of ahoy.
- AHOY_COMMAND_NAME: the name of the command being run (e.g. test), so wrapped scripts
can detect that they were invoked via ahoy, and which command triggered them. Resolves
#165.
Better help output
Two-tier help with per-command DESCRIPTION sections, as long as you add them to your .ahoy.yml files.
Bug fixes
- Fixed nil-pointer panics in edge-case command execution paths
- Fixed silent error swallowing and incorrect exit codes on invalid flags
- Fixed a stderr-capture deadlock by replacing buffering with a goroutine drain
- Fixed atomic file writes and URL scheme validation in downloadFile
- Fixed AHOY_FILE and AHOY_VERBOSE environment variable wiring
Internal changes
Framework migration
- Replaced urfave/cli with spf13/cobra, a more widely used CLI tool library that has more features we can use
- CLI flags are handled directly via Cobra and spf13/pflag
- Added a custom pre-parser so the small amount of single-dash flags we have (-version, -help) keep on working
- Added expandPath() for unified, consistent file path handling
Project structure
v3 code now lives at the repository root. The v2 code is preserved in the v2/ subdirectory for posterity and continued support.
CI
- Tests run against both the v2 and root (v3) codebases
- Added Homebrew coreutils to the macOS runners so timeout works in the BATS suite
Full changelog: v2.5.0...v3.0.0

New features! ✨ ✨
- Multiple .env files support - You can now specify multiple environment files using array syntax, addressing #136. Files are loaded in order with later files overriding earlier ones. Thanks to @jackwrfuller for the initial implementation that was incorporated into this feature!
# Single env file (backwards compatible)
env: .env
# Multiple env files (new array syntax)
env:
- .env.base
- .env.local
- .env.override
# Command-level multiple env files
commands:
deploy:
env:
- .env.deploy
- .env.secrets
Bug fixes 🐛 👏
- Windows compatibility improvements - A big welcome back to original maintainer @frankcarey who fixed path handling and binary execution issues on Windows platforms. Thanks to Frank for identifying and helping resolve these Windows issues! 🙌
What's Changed
- Add comprehensive test coverage for multiple env files feature with 25+ unit and integration tests
- Implement StringArray type for flexible YAML parsing of both single strings and arrays
- Maintain full backwards compatibility with existing .ahoy.yml files
- Add graceful handling of non-existent env files (they are silently skipped)
- Support for comments and empty lines in env files
- Proper environment variable precedence: command-level overrides global, later files override earlier ones
Technical Details
The multiple env files feature uses a new StringArray type that handles both the old single string format and the new array format in YAML. This ensures 100% backwards compatibility - existing .ahoy.yml files will continue to work without any changes.
Full Changelog: v2.4.0...v2.5.0

Bug fix 🐛 👏
- Use Environ() instead of Env by @jnsalsa in #140 - this prevents existing environment variables from all being cleared out when using then env option in your command file.
What's Changed
- chore: Update Dependabot config for v2 by @ocean in #134
- Linting and config updates by @ocean in #141
New Contributors
- @jnsalsa made their first contribution in #140
Full Changelog: v2.3.0...v2.4.0

New features! ✨ ✨
- Add support for .env files in commands by @jackwrfuller in #126
- Add Oh-My-Zsh plugin by @jackwrfuller in #128
What's Changed
- chore: Remove outdated docs build tools by @ocean in #123
- Create FUNDING.yml by @ocean in #124
- Update Zsh completions and add Oh-My-Zsh plugin by @jackwrfuller in #128
- Fix broken installation command by @jackwrfuller in #127
- Linting corrections by @ocean in #131
- Move code to v2 directory as this is correct for v2 of a Go project by @ocean in #132
- Update README to add info about .env file support by @ocean in #133
New Contributors
- @jackwrfuller made their first contribution in #128
Full Changelog: v2.2.0...v2.3.0

What's Changed
- Create code of conduct by @ocean in #102
- Update issue templates by @ocean in #103