Skip to content

Add support for rafn - benchmark parsing and storage tool - #1935

Merged
taiki-e merged 4 commits into
taiki-e:mainfrom
DarkWanderer:add-rafn-support
Jul 23, 2026
Merged

taiki-e merged 4 commits into
taiki-e:mainfrom
DarkWanderer:add-rafn-support

Conversation

@DarkWanderer

@DarkWanderer DarkWanderer commented Jul 11, 2026 •

Copy link
Copy Markdown
Contributor

What

Adds a built-in manifest entry for rafn, a benchmark uploader CLI, so taiki-e/install-action can resolve it without falling back to cargo-binstall.

Details

  • Repository: voron-software/rafn, published to crates.io as rafn, releases tagged vX.Y.Z.
  • Assets: rafn-<rust-target>.tar.gz (Linux gnu x86_64/aarch64, macOS x86_64/aarch64) and rafn-x86_64-pc-windows-msvc.zip (Windows), binary at archive root — no musl builds are published.
  • License: Apache-2.0.
  • Generated with ./tools/manifest.sh rafn and ./tools/update-markdown.sh.

Rafn already installs successfully today via the cargo-binstall fallback path (it has cargo-binstall metadata configured); this PR adds it to the built-in manifest for faster resolution.

@DarkWanderer
DarkWanderer marked this pull request as ready for review July 11, 2026 14:12
@DarkWanderer
DarkWanderer marked this pull request as draft July 11, 2026 14:13
@DarkWanderer
DarkWanderer marked this pull request as ready for review July 11, 2026 14:40
@DarkWanderer DarkWanderer changed the title Support rafn Add support for rafn - benchmark parsing and storage tool Jul 23, 2026

@taiki-e taiki-e left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@taiki-e
taiki-e merged commit 54ede98 into taiki-e:main Jul 23, 2026
81 checks passed
@taiki-e

taiki-e commented Jul 23, 2026

Copy link
Copy Markdown
Owner

Published in 2.85.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants