Skip to content

Include man pages in release archives#4724

Open
mvanhorn wants to merge 1 commit intojunegunn:masterfrom
mvanhorn:feat/include-man-pages-release
Open

Include man pages in release archives#4724
mvanhorn wants to merge 1 commit intojunegunn:masterfrom
mvanhorn:feat/include-man-pages-release

Conversation

@mvanhorn
Copy link
Copy Markdown

Summary

  • Replace non-existent* glob in .goreleaser.yml archives.files with explicit paths to man/man1/fzf.1 and man/man1/fzf-tmux.1
  • Release tarballs (tar.gz) and zip archives will now include the man pages alongside the fzf binary
  • No changes to the binary, build process, or install scripts

Motivation

Closes #4229. The man pages are already maintained in the repository but were excluded from release archives by the goreleaser config. Including them makes it easier for package maintainers and users who download release assets directly to install the documentation.

Test plan

  • Verify with goreleaser build --clean --snapshot that archives contain man pages
  • Confirm existing binary packaging is unchanged

This contribution was developed with AI assistance (Claude Code).

Add fzf.1 and fzf-tmux.1 man pages to the goreleaser archive
configuration so they are bundled alongside the binary in release
tarballs and zip files.

Previously, the archives section used a `non-existent*` glob to
exclude all extra files. Replace this with explicit paths to the
man pages that are already maintained in the repository.

Closes junegunn#4229
@mvanhorn mvanhorn mentioned this pull request Mar 20, 2026
10 tasks
@github-actions github-actions bot added the build Build system label Mar 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

build Build system

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Include manual in a release asset

1 participant