Skip to content

fix(run): push tags to dummy remote so semantic-release stops failing#141

Merged
BryanFRD merged 1 commit into
mainfrom
fix/dummy-remote-push-tags
Jun 15, 2026
Merged

fix(run): push tags to dummy remote so semantic-release stops failing#141
BryanFRD merged 1 commit into
mainfrom
fix/dummy-remote-push-tags

Conversation

@BryanFRD

Copy link
Copy Markdown
Contributor

Why semantic-release is missing from the perf comparison table

When the bench runner reaches the semantic-release step it does:

[semantic-release] ✘ An error occurred while running semantic-release:
ExecaError: Command failed with exit code 128: git fetch --tags /tmp/tmp.NXu6Tet4op

setup_dummy_remote does git init --bare + git push origin HEAD but no tags. semantic-release's planning phase fetches tags very early to resolve the previous release, sees an empty tag set, and dies with exit 128 — run.sh then reports SKIP: command failed for every (fixture, semantic-release) pair.

Same root cause is going to bite any future Node-based tool that derives version state from tags (which is most of them).

Fix

One extra git push --tags after the git push HEAD. -q keeps the output silent and || true matches the existing pattern — even on fixtures with no tags it's a no-op, not an error.

After this lands, semantic-release should start appearing as a real comparison row in the npm section of the perf table.

@BryanFRD BryanFRD merged commit a0cfa04 into main Jun 15, 2026
14 checks passed
@BryanFRD BryanFRD deleted the fix/dummy-remote-push-tags branch June 15, 2026 16:25
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.

1 participant