Released on February 8, 2026, bulkfilepr v0.2.0 introduces a powerful enhancement to how you maintain standardized files across your organization’s repositories. This release focuses on increasing the flexibility of the tool’s matching capabilities, making it significantly easier to roll out updates to repositories that may be at different stages of their version history.

What’s new

The headline feature of v0.2.0 is the introduction of multi-version matching in the match update mode.

Previously, when using the --mode match flag, you had to provide a single expected SHA-256 hash. If a file didn’t match that exact hash, the update was skipped. Now, the --expect-sha256 parameter supports a comma-separated list of hashes.

If the target file in a repository matches any of the hashes provided in your list, bulkfilepr will proceed with the update. To help you debug mismatches, the tool now provides a detailed error message listing all the expected hashes it was looking for, alongside the actual hash found in the repository.

Along with this feature, we’ve updated the documentation in docs/USAGE.md and docs/EXAMPLES.md to provide clear patterns and examples for utilizing this new multi-hash support.

Why it matters

Maintaining consistency across dozens or hundreds of repositories is rarely a linear process. In a real-world environment, different teams might have adopted different versions of a standard workflow or config file, or some repositories might have lagged behind previous updates.

By supporting multiple expected hashes, bulkfilepr removes the need to run multiple separate update passes for every possible historical version of a file. You can now target all “legacy” versions in a single command, ensuring that your entire fleet moves toward the current standard more efficiently and with less manual overhead.

Getting started with v0.2.0

This is a non-breaking release, meaning your existing workflows and single-hash commands will continue to work exactly as they did before.

To upgrade to v0.2.0, simply update the binary via your preferred installation method. Once updated, you can start using the new multi-matching capability by passing multiple hashes:

bulkfilepr --mode match --expect-sha256 "hash1,hash2,hash3" ...

Whether you are managing GitHub Actions workflows, CODEOWNERS files, or linting configurations, v0.2.0 makes the process of staying synchronized across your codebase smoother and more resilient.

This post was AI-generated using the model unsloth/gemma-4-31B-it-GGUF:UD-Q5_K_XL. Reference: UnitVectorY-Labs/bulkfilepr, v0.2.0, generated on 2026-04-10. Author: release-storyteller