Skip to content

fix(ci): pass --repo to gh calls in release-please's PyPI-publish trigger - #73

Merged
petercorke merged 2 commits into
mainfrom
fix/release-please-gh-repo
Aug 13, 2026
Merged

fix(ci): pass --repo to gh calls in release-please's PyPI-publish trigger#73
petercorke merged 2 commits into
mainfrom
fix/release-please-gh-repo

Conversation

@petercorke

Copy link
Copy Markdown
Owner

Summary

  • The "Trigger PyPI publish" step in release-please.yml has no actions/checkout, so gh can't infer the target repo from a git remote and fails with fatal: not a git repository.
  • Pass --repo explicitly (via GH_REPO env) to both gh release list and gh workflow run so the step doesn't depend on git state at all.

Seen failing here: https://github.com/petercorke/machinevision-toolbox-python/actions/runs/31649562305

Test plan

  • Next release-please run that creates a release should successfully dispatch release.yml against the new tag.

🤖 Generated with Claude Code

…gger

The "Trigger PyPI publish" step has no actions/checkout, so gh can't
infer the target repo from a git remote and fails with "not a git
repository". Pass --repo explicitly via GH_REPO instead.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@petercorke
petercorke enabled auto-merge (squash) August 12, 2026 23:46
@codacy-production

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

@petercorke
petercorke merged commit 6ff01a3 into main Aug 13, 2026
17 checks passed
@github-actions github-actions Bot mentioned this pull request Aug 13, 2026
petercorke added a commit that referenced this pull request Aug 13, 2026
…hy-string bug (#74)

steps.release.outputs.releases_created is always the literal string
"true" or "false" (release-please-action stringifies a JS boolean via
core.setOutput), never unset. Only "" is falsy in an if: expression, so
the bare output reference fired the trigger on every push to main, not
just when a release was actually created -- confirmed live: it fired
after PR #73 merged (a non-release push) and dispatched release.yml
against the already-published v2.2.0 tag.

Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
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