Skip to content

chore: sync upstream changes (c75c32e5)#56

Merged
willdurand merged 8 commits into
amofrom
sync/upstream-c75c32e5
Jun 3, 2026
Merged

chore: sync upstream changes (c75c32e5)#56
willdurand merged 8 commits into
amofrom
sync/upstream-c75c32e5

Conversation

@willdurand

@willdurand willdurand commented Jun 3, 2026

Copy link
Copy Markdown
Member

Fixes #55

Commits included

| * c75c32e5 zdiff (upstream/main, upstream/HEAD) ci: update GitHub Action versions (#667) (3 hours ago)
| * 30123f73 Francisco Pombal fix: change release archive extension from .gz to .tar.gz (#669) (3 hours ago)
| * 73a3059a zdiff ci: test recent versions of go and python (#671) (3 hours ago)
| * 7a349f0e zdiff chore: go fix (#672) (3 hours ago)
| * e9ee494c Victor M. Alvarez feat: add `--cpu-limit` option to scan command (20 hours ago)
| * 9dc53fe2 Victor M. Alvarez docs: document changes in `yr fmt`. (20 hours ago)
| * 1918f38f Victor M. Alvarez feat: allow `fmt` command to process directories recursively (21 hours ago)

plusvic and others added 8 commits June 2, 2026 15:17
The `yr fmt` command can now accept directory paths in addition to individual file paths. When a directory is provided, it will format all YARA files (`.yar`, `.yara`) found within it.

By default, only files in the top-level directory are processed. A new `-r` or `--recursive` option has been added to enable scanning for YARA files in subdirectories, allowing users to specify a maximum recursion depth. This improves usability by simplifying formatting across multi-file projects.

Closes #271
This option allows users to dynamically limit the CPU utilization of the scan process. It helps prevent CPU saturation when running background scan tasks on production servers or multi-user systems.

The limit is achieved by measuring the active time spent scanning each file and introducing a calculated sleep delay before processing the next file.

Closes #115.
Go recently updated go fix: https://go.dev/blog/gofix

Ran go fix ./... on go directory
Ran tests with go 1.18 and 1.26
Python 3.9 went end-of-life on Halloween in 2025 and all Go versions prior to 1.25 went end-of-life on or before February 11th, 2026. I didn't feel comfortable deprecating support for older versions in a PR focused on CI tests.
Release archives for non-Windows targets are gzip-compressed TAR files (`tar czf`) but were being named with a `.gz` extension, causing interoperability issues with tooling that infers format from the extension. Windows `.zip` builds are unaffected. Downstream consumers fetching assets by exact filename will need to update from `.gz` -> `.tar.gz`.

Co-authored-by: Copilot <198982749+Copilot@users.noreply.github.com>
@willdurand willdurand merged commit 57fc660 into amo Jun 3, 2026
20 checks passed
@willdurand willdurand deleted the sync/upstream-c75c32e5 branch June 3, 2026 10:18
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.

Upstream sync failed: merge conflict (c75c32e5)

4 participants