release: prepare setup-benchmark-go-action v1.0.4

[cpunion]

Summary

• publish the paired same-runner baseline and commit-indexed storage changes as v1.0.4
• update only package release metadata

Validation

• npm run check (31 tests passed)
• npm run build
• git diff --exit-code -- dist publish/dist

[github-actions]

setup-benchmark-go-action

9c4de3cf7706 | workflow run | long-term charts

Action bundle sizes

Bundle	Size	vs main
RecordBundle	326529 B	+0.0%
RenderBundle	327120 B	+0.0%

Parser and validation operations

Group	Benchmark	Median time	vs main
Grouping	GroupRules100	237037.783 ns/op	+2.6% (worse)
Parsing	ParseGoOutput40	380732.795 ns/op	+39.7% (worse)
Validation	ValidateArtifact40	350736.774 ns/op	+14.1% (worse)

Compared only with the latest matching platform in the main series.

[fennoai]

Review Summary

Release PR bumping the project version 1.0.3 → 1.0.4 in package.json and package-lock.json. Reviewed across code-quality, performance, security, and documentation dimensions.

No issues found. The change is clean and self-consistent:

• Consistency — package.json:3 and the two package-lock.json version fields (:3, :9) all move together to 1.0.4; no stale 1.0.3 reference remains anywhere in the tree.
• Lockfile integrity — only the two project-version fields changed; no dependency versions, resolved URLs, integrity hashes, or lifecycle scripts were altered. Supply-chain surface is unaffected.
• Docs — README/action.yml pin the action via the floating @v1 major tag (config version: 1 is the schema, not the package version), so no docs are made stale by a patch bump. There is no CHANGELOG in the repo, so none is left out of date.

Non-blocking reminder (release process, outside this diff): consumers pin xgo-dev/setup-benchmark-go-action@v1, so the floating v1 tag will need to be re-pointed to the release commit after merge for downstream users to receive 1.0.4.