bat 0.13 release

[sharkdp]

Changes since 0.12.1: https://github.com/sharkdp/bat/compare/v0.12.1...master

• [x] Write release notes (according to the usual format https://github.com/sharkdp/bat/releases/tag/v0.12.0)
• [x] Check for outdated dependencies (https://deps.rs/repo/github/sharkdp/bat)
• [x] Run cargo update to update dependencies to the latest compatible (minor) version.
• [x] Run cargo fmt
• [x] Update syntaxes and themes (assets/create.sh).
• [x] Update README (features, usage, languages, ..).
• [x] Update man page.
• [x] Review -h/--help text.
• [x] Update version in Cargo.toml. Run cargo build to update Cargo.lock. Update the version in all README files (translations).
• [x] Run cargo install -f --path . and locally test the new release
• [x] cargo publish --dry-run --allow-dirty.
• [x] git tag vX.Y.Z; git push --tags
• [x] publish to crates.io by cloning a fresh repo and calling cargo publish.
• [x] Inform package maintainers about the update:
  
  
  
  • https://www.archlinux.org/packages/community/x86_64/bat/
  
  

See also: My release checklist for Rust programs

[sharkdp]

I have added a few tickets to the v0.13 milestone. Let's try to work on these before releasing v0.13:

https://github.com/sharkdp/bat/milestone/6

[wookietreiber]

@sharkdp I just stumbled upon your checklist -- just wanted to let you know that on Arch Linux bat has moved from AUR to the community repo.

[sharkdp]

Oh right, the checklist is outdated. We already link to the correct package in the README: https://github.com/sharkdp/bat#on-arch-linux

Updating the checklist...

[sharkdp]

v0.13 has been released: https://github.com/sharkdp/bat/releases/tag/v0.13.0

[ignatenkobrain]

@sharkdp would be nice if you could inform me too since I'm packaging bat for Fedora.

[sharkdp]

@sharkdp would be nice if you could inform me too since I'm packaging bat for Fedora.

Will do, added to my checklist for future releases. Thank you very much for your work!

[pizzamig]

Hi. I'm the package maintainer for FreeBSD. Thanks for your amazing project.
I've a small issue with man page installation.
In 0.13 the man page [and the shell completion files that I want to add to the package] are now generated from a template during the build phase, it's not installed/copied via cargo install, it's buried in the target folder (something like target/release/build/bat-0e2b1a64c228c1b3/out/assets/. with the bat folder that contains a hash (I don't know how is generated and how often it will change).
Is there a way to install those artifacts during cargo install or deterministically know the path for those files outside cargo?

[sharkdp]

@pizzamig Thank you for the feedback and for your work!

We have the same problem when building the Debian packages in CI. We actually use a * glob to get around this:
https://github.com/sharkdp/bat/blob/8d3136eb6f94a1a4dffd9cf6a88d083c693d1616/ci/before_deploy.bash#L41

This is obviously not a great solution, but I don't really know if there is a better way :-/

[pizzamig]

I'm testing find target -name bat.1 -exec cp {} $DESTDIFR \; and it seems to work,
I guess it's something missing from cargo, the extra artifacts are not installed with cargo install and there is no way to tell cargo about them...
Thanks for the tip!